5.4.0 failure
5.4.0 failure
5.4.0 fails or it exits without notification not sure which
preflight is good (bunch of warnings no errors)
config good
I am not intentionally using a ramdisk
Help
preflight is good (bunch of warnings no errors)
config good
I am not intentionally using a ramdisk
Help
-
dwhitfield
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: 5.4.0 failure
Is this an upgrade or a new install? If new install, can you post your install.log? If it is an upgrade, can you post your upgrade.log? CentOS or RHEL and what version?
Re: 5.4.0 failure
Could you provide more detail -- When it fails / exits are you talking about the UI only or does the monitoring engine fail or both?
From what log does the implied usage of ramdisk come from? Can you post that here as well as any other error messages you've seen?
Anything of interest in the event log?
Home > Monitoring Process > Event Log
Check to see if there are multiple Nagios processes running, as this will cause an array of problems.
run this cmd on your nagios server:
ps - aef | grep nagios.cfg
* Look for multiple parent (PPID) processes. The Nagios process forks itself to run checks therefore subprocesses are normal. The nagios user should probably be the only owner of the nagios process. If in any doubt post the output here.
If there are multiple Nagios processes running, run these commands to resolve:
From what log does the implied usage of ramdisk come from? Can you post that here as well as any other error messages you've seen?
Anything of interest in the event log?
Home > Monitoring Process > Event Log
Check to see if there are multiple Nagios processes running, as this will cause an array of problems.
run this cmd on your nagios server:
ps - aef | grep nagios.cfg
* Look for multiple parent (PPID) processes. The Nagios process forks itself to run checks therefore subprocesses are normal. The nagios user should probably be the only owner of the nagios process. If in any doubt post the output here.
If there are multiple Nagios processes running, run these commands to resolve:
Code: Select all
service nagios stop
killall -9 nagios
service nagios startBe sure to check out the Knowledgebase for helpful articles and solutions!
Re: 5.4.0 failure
it is centos 6.7 64bit
Here is the upgrade.log there were no failures that I found
only one nagios running
nothing interesting in events
Here is the upgrade.log there were no failures that I found
only one nagios running
Code: Select all
[root@nagiosxi ~]# ps -aef | grep nagios.cfg
root 22124 21841 0 11:06 pts/0 00:00:00 grep nagios.cfgYou do not have the required permissions to view the files attached to this post.
-
dwhitfield
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: 5.4.0 failure
ok, I misunderstood your original post. I was thinking the upgrade failed. What's the output of cat /var/log/messages | grep segfault? Please use a code block for the output.
Also, please attach screenshots of any GUI errors.
Also, please attach screenshots of any GUI errors.
Re: 5.4.0 failure
cat /var/log/messages | grep segfault brings up nothing
The only GUI indication is
The only GUI indication is
You do not have the required permissions to view the files attached to this post.
-
dwhitfield
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: 5.4.0 failure
That XML error is the only one you have seen? Are you forcing SSL in any way? Are you using Mod gearman or mk-livestatus? Have you upgrading pnp4nagios or any of the tools XI uses separately from the upgrade?
Lastly, please post your /usr/local/nagios/etc/nagios.cfg
Lastly, please post your /usr/local/nagios/etc/nagios.cfg
Re: 5.4.0 failure
none of those are in use ... SSL is in use. This was built in to the VM
You do not have the required permissions to view the files attached to this post.
Re: 5.4.0 failure disregard
We restored from backup to prior to the upgrade
we are back up
Thanks for your help
we are back up
Thanks for your help
Re: 5.4.0 failure
Glad to hear you're back up and running. We'll go ahead and lock this thread now, thanks.
Be sure to check out the Knowledgebase for helpful articles and solutions!