Page 2 of 3

Re: Nagios XI hanging at 100% CPU usage

Posted: Mon Jun 26, 2017 9:28 am
by dwhitfield
What's the output of the following?

Code: Select all

find / -name my.cnf
sestatus
If those don't show anything obvious, can you attach or PM your sudoers file? Again, if you PM, make sure you update the thread.

UPDATE: my.cnf shared with techs

Re: Nagios XI hanging at 100% CPU usage

Posted: Mon Jul 10, 2017 1:38 pm
by wa16
The issue occurred again :(

I was able to open the cnf file so I PM'ed you the content. Please let me know if you need anything else or if there is anything else I can try to resolve this issue.

Thanks!

Re: Nagios XI hanging at 100% CPU usage

Posted: Mon Jul 10, 2017 2:08 pm
by dwhitfield
Since the profile is now well over two weeks old, can you send another, so that we have fresh logs? Also, what's the output of sestatus?

You can download the profile by going to Admin > System Config > System Profile and click the ***Download Profile*** button towards the top. If for whatever reason you *cannot* download the profile, please put the output of View System Info (5.3.4+, Show Profile if older) in the thread (that will at least get us some info). This will give us access to many of the logs we would otherwise ask for individually. If security is a concern, you can unzip the profile take out what you like, and then zip it up again. We may end up needing something you remove, but we can ask for that specifically.

After you PM the profile, please update this thread. Updating this thread is the only way for it to show back up on our dashboard.

UPDATE: Profile received

Re: Nagios XI hanging at 100% CPU usage

Posted: Mon Jul 10, 2017 2:44 pm
by wa16
Thanks.

Output of sestatus is "SELinux status: disabled"

I PM'ed you an updated profile download as well.

Thanks!

Re: Nagios XI hanging at 100% CPU usage

Posted: Tue Jul 11, 2017 11:28 am
by tgriep
I took a look at the System Profile and everything seems to be OK except that the system's memory is still at 3 Gig so the change to 6 Gig did not happen for some reason.
Verify that the VMWare image has 6 Gig allocated to it and reboot the system to make sure it recognizes all of the memory.

Re: Nagios XI hanging at 100% CPU usage

Posted: Tue Jul 11, 2017 12:28 pm
by wa16
Thanks. That is odd, VMware is definitely showing 6GB and I have done a complete shut down and reboot ever since as well. Is there anything else I need to do to make sure the 6GB of memory is reflected in Nagios?

Re: Nagios XI hanging at 100% CPU usage

Posted: Tue Jul 11, 2017 12:50 pm
by tgriep
I missed it in the first post. You are running 32bit of Centos5 and you need to be running a different linux kernel for it to recognize the additional memory.
Take a look as this link for more details.
https://www.centos.org/forums/viewtopic.php?t=27235

Re: Nagios XI hanging at 100% CPU usage

Posted: Tue Jul 11, 2017 6:17 pm
by wa16
Got it. When I try a "yum install kernel-PAE", I get the following. Any ideas? I already attempted a "yum update" which completed successfully:


[root@nagios ~]# yum install kernel-PAE
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* epel: pubmirror2.math.uh.edu
http://apt.sw.be/redhat/el5/en/i386/dag ... repomd.xml: [Errno 4] IOError: <urlopen error (-2, 'Name or service not known')>
Trying other mirror.
Setting up Install Process
No package kernel-PAE available.
Nothing to do

Re: Nagios XI hanging at 100% CPU usage

Posted: Wed Jul 12, 2017 10:15 am
by tgriep
Centos5 was de-supported earlier this year so maybe the PAE kernel is not available or that the repository is now gone.
If you stay on Centos5, you would have to upgrade to 5.11 to get access to the last updates to Centos 5.11.
http://vault.centos.org/5.11/

I suggest migrating to Centos 6 or 7 as they are still supported.

Re: Nagios XI hanging at 100% CPU usage

Posted: Wed Jul 12, 2017 5:56 pm
by wa16
Got it, thanks.

As far as the CPU usage getting to 100% and the system getting stuck there, what could be causing that? What changes can I make to the existing system to hopefully resolve this?