Apply Config throws error but says no error

[SavaSC]

Do you see any config errors when go to the CCM > Tools > Config File Management, and click on the following buttons in the exact same order: Delete Files, Write Configs, and Verify Files?

If you don't see any errors, try to apply configuration. If this still fails, run the following commands, and show the output:

Code: Select all

chage -l nagios
chage -l apache
sestatus
ls -la /usr/local/nagiosxi/scripts/nagiosql*

Also, start a running tail on the cmdsubsys.log, and redirect the output to a text file:

Code: Select all

tail -f /usr/local/nagiosxi/var/cmdsubsys.log &> /tmp/debug.txt

While the tail is running, apply configuration in the web UI. When this is done (you see an error in the web UI), go back to the terminal, and stop the tail by pressing "Ctrl + c". Next, post the "debug.txt" file that was generated in the "/tmp" directory.

It went through the Delete Files and Write Configs just fine. However, when I did a Verify Files it showed a blank pink box just like when I Apply Configuration and ask to see the errrors. I have attached a screenshot. Also, attached screenshots of the commands you requested and the debug file.

Thank you.

[scottwilkerson]

For some reason one of the scripts that needs to run as part of the process cannot be run successfully, and we are going to need the errors of the following

Can you post the output of the following commands run from the command line:

Code: Select all

cat /etc/group|grep nag

and also

Code: Select all

sudo su nagios -c "/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg"

[SavaSC]

I have attached the screenshots that you have requested.

Also, this morning when I got to work I found that the monitoring engine had stopped. I was able to turn it on again, no problem. That has never happened before, to my recollection. So I thought you should know.

Thanks.

[lmiltchev]

I suspect that you may be running into some permissions issues, as I see the following in the debug.txt file:

tar: usr/local/nagios/etc/import: Cannot utime: Operation not permitted
tar: usr/local/nagios/etc/services: Cannot utime: Operation not permitted
tar: usr/local/nagios/etc/pnp/check_commands: Cannot utime: Operation not permitted
tar: usr/local/nagios/etc/pnp/pages: Cannot utime: Operation not permitted
tar: usr/local/nagios/etc/pnp: Cannot utime: Operation not permitted
tar: usr/local/nagios/etc/static: Cannot utime: Operation not permitted
tar: usr/local/nagios/etc/hosts: Cannot utime: Operation not permitted
tar: usr/local/nagios/etc: Cannot utime: Operation not permitted
tar: Exiting with failure status due to previous errors
/usr/local/nagiosxi/scripts
RESETTING PERMS
OUTPUT=RESETTING PERMS
RETURNCODE=1

Can you run the following command:

Code: Select all

ll -R /usr/local/nagios/etc/ > /tmp/perms.txt

then upload the perms.txt file on the forum?

Also, try resetting your permissions, by running:

Code: Select all

cd /usr/local/nagiosxi/scripts/
./reset_config_perms.sh

Do you see any config errors now, when you click through Delete Files > Write Configs > Verify Files under the "Config File management" page?

[SavaSC]

Running the command did not fix the issue, but it did change slightly. Now when I go to Verify Files it gives me an empty blue box instead of a red one. As y'all normally use blue to indicate success, I assume it went fine. I tried to apply config after that, but it did the same thing.

I have attached the requested file.

Thank you.

[SavaSC]

The monitoring engine has spontaneously shut down again. What logs do you need to diagnose this? We need to do something. We can't have Nagios stop monitoring over the weekend.

[scottwilkerson]

@SavaSC - Can you open a ticket by emailing [email protected] and include a reference to this thread and a System Profile zip from Admin -> System Profile

Thanks

[SavaSC]

@SavaSC - Can you open a ticket by emailing [email protected] and include a reference to this thread and a System Profile zip from Admin -> System Profile

Thanks

I have done this, thanks.

[dwhitfield]

Locking, as ticket received.