I seem to have to reboot my 2.0.5 Syslog Server about once a week. Otherwise, it will hang when navigating after logging into the web GUI - does not matter which page I am requesting. Should I look to upgrading the server to 2.0.6? The server is a single instance with a 70GB DB at the moment, 372 shards, 38 indices. I am not keeping logs older than 30 days so it can run lean and mean. /dev/sda1 is only 16% utilized at the moment. CPU bounces around 50% and physical RAM is only 14% used.
If you recommend an upgrade to 2.0.6, is this a forklift upgrade? As in, not much different than starting from scratch or is there an actual "upgrade process"?
Thanks for any direction you can give!!! I am new to Nagios Syslog Server but LOVE it so far!!!
Syslog Server version 2.0.5 Reboot
Re: Syslog Server version 2.0.5 Reboot
Are there any messages logged to /var/log/messages, /var/log/httpd/* or /var/log/elasticsearch/<cluster_uuid>.log when it gets in this state? A profile taken while it is in the hung state would be useful. This can be generated from the command line:
/usr/local/nagioslogserver/scripts/profile.sh
and willl create the profile:
/tmp/system-profile.tar.gz
The messages are not the same, but the same memory option in https://support.nagios.com/kb/article/n ... y-132.html can impact the web UI. I'd suggest upping that for good measure.
/usr/local/nagioslogserver/scripts/profile.sh
and willl create the profile:
/tmp/system-profile.tar.gz
The messages are not the same, but the same memory option in https://support.nagios.com/kb/article/n ... y-132.html can impact the web UI. I'd suggest upping that for good measure.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Syslog Server version 2.0.5 Reboot
Hello - thank you for the prompt reply. I will certainly look to the message logs when it does it again and create the profile. Unfortunately, I have rebooted since then because it was not taking in any logs this time. Does this topic stay open until resolved or how does this work exactly?
Re: Syslog Server version 2.0.5 Reboot
BTW - I tried upping the RAM available to the GUI per the URL and get the following error message:
root@mpls01-nagios01:~# sed -i 's/^memory_limit.*/memory_limit = 512M/g' /etc/php.ini
sed: can't read /etc/php.ini: No such file or directory
Is this because of the distro I am using?
Ubuntu 16.04.5 LTS (GNU/Linux 4.4.0-116-generic x86_64)
root@mpls01-nagios01:~# sed -i 's/^memory_limit.*/memory_limit = 512M/g' /etc/php.ini
sed: can't read /etc/php.ini: No such file or directory
Is this because of the distro I am using?
Ubuntu 16.04.5 LTS (GNU/Linux 4.4.0-116-generic x86_64)
Re: Syslog Server version 2.0.5 Reboot
These are the php.ini files I have on my system:
root@mpls01-nagios01:/# find / -name php.ini
/etc/php/7.0/cli/php.ini
/etc/php/7.0/apache2/php.ini
/etc/php/7.0/cgi/php.ini
I am assuming it is the "apache2" instance, correct?
root@mpls01-nagios01:/# find / -name php.ini
/etc/php/7.0/cli/php.ini
/etc/php/7.0/apache2/php.ini
/etc/php/7.0/cgi/php.ini
I am assuming it is the "apache2" instance, correct?
Re: Syslog Server version 2.0.5 Reboot
Yes, that didn't work because of the location and files on the Ubuntu system are different. You can try manually modifying the file as a test, but a requirement is to use a Cent or RHEL OS:
https://assets.nagios.com/downloads/nag ... Server.pdf
https://assets.nagios.com/downloads/nag ... Server.pdf
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.