Search found 23 matches
- Tue Jun 05, 2018 11:35 am
- Forum: Nagios Log Server
- Topic: waiting for elasticsearch database...
- Replies: 5
- Views: 958
Re: waiting for elasticsearch database...
it did go green after like 2 hours, it caught up and we are good. looks good, thanks.
- Mon Jun 04, 2018 11:33 am
- Forum: Nagios Log Server
- Topic: waiting for elasticsearch database...
- Replies: 5
- Views: 958
Re: waiting for elasticsearch database...
went ahead and bumped up the memory on both instances from 12GB to 16GB and the primary instance came online...cluster health yellow.
guessing it was a heapsize issue? I will monitor and make sure it catches up and goes green again.
guessing it was a heapsize issue? I will monitor and make sure it catches up and goes green again.
- Mon Jun 04, 2018 11:18 am
- Forum: Nagios Log Server
- Topic: waiting for elasticsearch database...
- Replies: 5
- Views: 958
Re: waiting for elasticsearch database...
Waiting for Database Startup
It looks like your local elasticsearch service is starting.
Why am I getting this error?
Elasticsearch can take a little while to start up because of it's indexing. This may take a few seconds.
The page will refresh automatically after 5 seconds...
It looks like your local elasticsearch service is starting.
Why am I getting this error?
Elasticsearch can take a little while to start up because of it's indexing. This may take a few seconds.
The page will refresh automatically after 5 seconds...
- Mon Jun 04, 2018 11:17 am
- Forum: Nagios Log Server
- Topic: waiting for elasticsearch database...
- Replies: 5
- Views: 958
waiting for elasticsearch database...
been at this for a long time, how long should it take to index (if it is?) - what log should I look at for errors/issues? tried restarting both servers in the cluster as per https://support.nagios.com/kb/article.php?id=550 one of the instances came up as normal like it should, the original still han...
- Thu Jan 25, 2018 5:31 pm
- Forum: Nagios Log Server
- Topic: updated to 2.0.2 - http issues
- Replies: 10
- Views: 867
Re: updated to 2.0.2 - http issues
This is your OVA (1.0.4 version), upgraded to 2.0.2 using your upgrade script following your steps, I've done yum update to see if updates to packages help. nothing else installed on this system, dedicated to nagios and only nagios. I have two instances, one in each datacenter. only my secondary dat...
- Thu Jan 25, 2018 2:19 pm
- Forum: Nagios Log Server
- Topic: updated to 2.0.2 - http issues
- Replies: 10
- Views: 867
Re: updated to 2.0.2 - http issues
just happened again, confirmed that php.ini is 512M.
I did service httpd status and it says httpd pid 1656 is running...
but not responding to http requests.
I did service httpd status and it says httpd pid 1656 is running...
but not responding to http requests.
- Thu Jan 25, 2018 12:00 pm
- Forum: Nagios Log Server
- Topic: updated to 2.0.2 - http issues
- Replies: 10
- Views: 867
Re: updated to 2.0.2 - http issues
actually, memory_limit is already set to 512M in /etc/php.ini
- Thu Jan 25, 2018 11:50 am
- Forum: Nagios Log Server
- Topic: updated to 2.0.2 - http issues
- Replies: 10
- Views: 867
Re: updated to 2.0.2 - http issues
not a problem, so basically after every time I update the software, I need to do set these settings?
looks like I set one for logstash, not for php.ini
looks like I set one for logstash, not for php.ini
- Wed Jan 24, 2018 6:14 pm
- Forum: Nagios Log Server
- Topic: updated to 2.0.2 - http issues
- Replies: 10
- Views: 867
Re: updated to 2.0.2 - http issues
attached logs for httpd, guessing thats what you wanted
disk space is not full
I'll try the service httpd status next time it dies
disk space is not full
I'll try the service httpd status next time it dies
- Wed Jan 24, 2018 4:24 pm
- Forum: Nagios Log Server
- Topic: updated to 2.0.2 - http issues
- Replies: 10
- Views: 867
updated to 2.0.2 - http issues
http server keeps going down on one instance (I monitor it from my network/server monitoring tool) I try to access the web interface when this alarm goes off, and yep, cant get to the web page, therefore no login. I reboot the VM to restore http for now. I did the memory changes for 1.0.4, do I have...