XI System Component Status: Failing

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
vmwareguy
Posts: 69
Joined: Wed Mar 16, 2016 9:41 am

XI System Component Status: Failing

Post by vmwareguy »

For whatever reason all of my services past Database Backend show a bad status. I have no idea where to even begin to trouble shoot this. I can't apply any new configurations. I ran a repair on the database and that didn't help. I'm running version 5.5.1

Any thoughts?

Thanks
You do not have the required permissions to view the files attached to this post.
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: XI System Component Status: Failing

Post by scottwilkerson »

All of these depend on crond running.

What is the output of the following:

Code: Select all

service crond status
chage -l nagios
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
vmwareguy
Posts: 69
Joined: Wed Mar 16, 2016 9:41 am

Re: XI System Component Status: Failing

Post by vmwareguy »

I see a bunch of nagios expired passwords
pam_unix(crond:account): account nagios has expired (failed to change password)
vmwareguy
Posts: 69
Joined: Wed Mar 16, 2016 9:41 am

Re: XI System Component Status: Failing

Post by vmwareguy »

is it as simple as changing the nagios password ?
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: XI System Component Status: Failing

Post by scottwilkerson »

This should do it

Code: Select all

chage -I -1 -m 0 -M 99999 -E -1 nagios
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
vmwareguy
Posts: 69
Joined: Wed Mar 16, 2016 9:41 am

Re: XI System Component Status: Failing

Post by vmwareguy »

scottwilkerson wrote:This should do it

Code: Select all

chage -I -1 -m 0 -M 99999 -E -1 nagios
This did it!! Thank you. What exactly did this change?
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: XI System Component Status: Failing

Post by scottwilkerson »

vmwareguy wrote:This did it!! Thank you. What exactly did this change?
It set the password for the nagios user to not expire for 99999 days.
Minimum Password Age to 0
Maximum Password Age to 99999
Password Inactive to -1
Account Expiration Date to -1
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
vmwareguy
Posts: 69
Joined: Wed Mar 16, 2016 9:41 am

Re: XI System Component Status: Failing

Post by vmwareguy »

So its working somewhat better but after about an hour I have two services showing errors now.
You do not have the required permissions to view the files attached to this post.
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: XI System Component Status: Failing

Post by scottwilkerson »

you may need to remove 2 lock file

Code: Select all

rm -f /usr/local/nagiosxi/var/dbmaint.lock
rm -f /usr/local/nagiosxi/var/event_handler.lock
Then they should kick off within about 5-10 minutes.
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
Locked