Page 1 of 1
"Waiting for configuration verification..... " is waiting
Posted: Sun May 12, 2019 5:54 am
by shaheazali
Hi Team,
We are seeing issue when we do "apply configurations" in Nagios XI . It shows as
"Waiting for configuration verification..... " and waiting forever.
We tried to restart ndo2db and nagios code and we tried to restore from snapshot.
It is blocking us from production support, so please help.
We tried to restore from the last backup but it breaks and it completely removed nagiosxi directory.
Version Used: Nagios XI 5.5.9.
Re: "Waiting for configuration verification..... " is waitin
Posted: Sun May 12, 2019 7:51 am
by gauravchauhan
We also checked the trailing. I guess the front end is not able to speak with the backend:
[root@adkdxxxxxxx sauxxx.matxxx]# tail -f /usr/local/nagiosxi/var/cmdsubsys.log
.............................................
PROCESSED 0 COMMANDS
...............Connection timed out after 15001 milliseconds
..............................................
PROCESSED 0 COMMANDS
...............Connection timed out after 15001 milliseconds
............................................
PROCESSED 0 COMMANDS
...............Connection timed out after 15001 milliseconds
..............................
Re: "Waiting for configuration verification..... " is waitin
Posted: Mon May 13, 2019 11:11 am
by cdienger
What is the output when you run:
Code: Select all
/usr/local/nagiosxi/scripts/reconfigure_nagios.sh
?
Please PM me a profile from the system so that I may review a few other things. The profile can be generated under Admin > System Config > System Profile > Download Profile.
Re: "Waiting for configuration verification..... " is waitin
Posted: Mon May 20, 2019 2:02 am
by shaheazali
Thank you,
The issue was with nagios user.
If got expired and because of which cron was not running.
We found the issue and it got resolved now.
Re: "Waiting for configuration verification..... " is waitin
Posted: Mon May 20, 2019 12:21 pm
by scottwilkerson
shaheazali wrote:Thank you,
The issue was with nagios user.
If got expired and because of which cron was not running.
We found the issue and it got resolved now.
Great! Glad it is resolved
Locking thread