Problem index log every day
-
- Posts: 19
- Joined: Tue Dec 02, 2014 12:43 pm
Problem index log every day
Hello everybody,
I am using nagioslog in cluster with two instances (64-bit ova)
Every morning, my Dashboard is empty and I must restart servers for rebuild index. On the web interface, service are UP then when I refresh page they are DOWN…
On ssh I got this :
[root@nagioslog ~]# service logstash status
Log stash Daemon dead but pid file exists
To resolve problem temporarily, I have created crontab which restart my servers every 5 hours. That seems resolve my problem, but I don’t think is the best solution…
Thanks for your help
PS:
For info, actually there are 72 hosts and 6,000,000 Docs per days.
I am using nagioslog in cluster with two instances (64-bit ova)
Every morning, my Dashboard is empty and I must restart servers for rebuild index. On the web interface, service are UP then when I refresh page they are DOWN…
On ssh I got this :
[root@nagioslog ~]# service logstash status
Log stash Daemon dead but pid file exists
To resolve problem temporarily, I have created crontab which restart my servers every 5 hours. That seems resolve my problem, but I don’t think is the best solution…
Thanks for your help
PS:
For info, actually there are 72 hosts and 6,000,000 Docs per days.
Re: Problem index log every day
What sort of CPU, memory, and disk space are available on the nodes? Are you hitting limits or high usage on any of those metrics?
Former Nagios employee
-
- Posts: 19
- Joined: Tue Dec 02, 2014 12:43 pm
Re: Problem index log every day
Hello,
VM nagioslog are working on ESX Intel Xeon 2 GHz, using 4vCPU, 4 Go & 1 file ".vmdk" of 100 Go (actually 50G used) for both.
Before, VM had 1 vCPU, since I add 3 vCPU, I don't hit limits.
Thanks for your help
VM nagioslog are working on ESX Intel Xeon 2 GHz, using 4vCPU, 4 Go & 1 file ".vmdk" of 100 Go (actually 50G used) for both.
Before, VM had 1 vCPU, since I add 3 vCPU, I don't hit limits.
Thanks for your help
Re: Problem index log every day
Are you saying you increased the limits and the problem went away? Or that you weren't hitting limits before and you still aren't now but the problem persists?
Former Nagios employee
-
- Posts: 19
- Joined: Tue Dec 02, 2014 12:43 pm
Re: Problem index log every day
Sorry for my english (I’m French )
Each morning, when I saw my Dashboard was empty, the web interface was very slow and CPU was 100%.
Then I add 3vCPU, and each morning the same problem (Dashboard empty, web interface slow) but CPU consume 157% of 400%
But the problem persists, except when I restart server.
Each morning, when I saw my Dashboard was empty, the web interface was very slow and CPU was 100%.
Then I add 3vCPU, and each morning the same problem (Dashboard empty, web interface slow) but CPU consume 157% of 400%
But the problem persists, except when I restart server.
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Problem index log every day
How much memory does this server have?
Does it have fast disks installed (e.g. SSD's)?
How much data per day are you sending this server?
Is this just a single server cluster, or do you have multiple machines sharing the workload?
Does it have fast disks installed (e.g. SSD's)?
How much data per day are you sending this server?
Is this just a single server cluster, or do you have multiple machines sharing the workload?
-
- Posts: 19
- Joined: Tue Dec 02, 2014 12:43 pm
Re: Problem index log every day
4GB of memoryHow much memory does this server have?
No fast disk, only 7200 RPMDoes it have fast disks installed (e.g. SSD's)?
We are sending between 6,100,000 & 6,800,000 Documents per dayHow much data per day are you sending this server?
In Primary Size it's between 2.8GB & 3,1GB
We have a cluster with 2 instances, with DNS round robin.Is this just a single server cluster, or do you have multiple machines sharing the workload?
All instances have same capacity (memory, Disk, vCPU).
Re: Problem index log every day
Make sure each server in the cluster is running the "elasticsearch" and "logstash" services:
If either of those are not running, please start them and wait a few minutes.
Code: Select all
service elasticsearch status
service logstash status
Former Nagios employee
-
- Posts: 19
- Joined: Tue Dec 02, 2014 12:43 pm
Re: Problem index log every day
tmcdonald wrote:Make sure each server in the cluster is running the "elasticsearch" and "logstash" services:
If either of those are not running, please start them and wait a few minutes.Code: Select all
service elasticsearch status service logstash status
When I execute command status is OK.
I monitor these service with Nagios XI.
If I don't restart servers nagioslog, total process will increases (500 process in 3 days), 100% of 400% CPU use by Java & and web interface very slow, but service elastic search and logstash are Ok with command service elasticsearch status.
I hope you understand my problem :/
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Problem index log every day
Would it be possible for us to get a list of the processes running when this happens?chris_Espoir wrote:total process will increases (500 process in 3 days),
Code: Select all
ps -ef