Page 2 of 2

Re: offline install

Posted: Thu Nov 01, 2018 3:01 pm
by ssax
Did it work after that? (Meaning you fixed the user issue and then re-ran the commands I sent again)

Re: offline install

Posted: Fri Nov 02, 2018 11:13 am
by duane909
Well, everything appears to be running now.
I tried adding a host using the CCM and so far (been about 9 minutes) it is just adding dots to the end of "Waiting for configuration verification"
~Duane

Re: offline install

Posted: Fri Nov 02, 2018 12:13 pm
by scottwilkerson
You could have a stuck lock file run the following

Code: Select all

rm -f /usr/local/nagiosxi/scripts/reconfigure_nagios.lock
If that doesn't do it lets verify that crond is running and you do not see errors here

Code: Select all

tail -f /var/log/cron

Re: offline install

Posted: Fri Nov 02, 2018 2:35 pm
by duane909
No lock files in the scripts directory.
I see about 10 lines of *.php for nagios showing up once every minute with no errors.
~Duane

Re: offline install

Posted: Fri Nov 02, 2018 2:41 pm
by scottwilkerson
duane909 wrote:No lock files in the scripts directory.
I see about 10 lines of *.php for nagios showing up once every minute with no errors.
~Duane
Can you share the output of the following after trying to start the apply configuration process

Code: Select all

tail -100 /usr/local/nagiosxi/var/cmdsubsys.log

Re: offline install

Posted: Tue Nov 06, 2018 12:15 pm
by duane909
I applied updates/patches to this server over the weekend and rebooted it.
Did not get a chance until now to look at this and it appears to be updating just fine.
Maybe one of my config changes or permissions changes did not take effect until I rebooted?
~Duane

Re: offline install

Posted: Tue Nov 06, 2018 3:10 pm
by scottwilkerson
duane909 wrote:I applied updates/patches to this server over the weekend and rebooted it.
Did not get a chance until now to look at this and it appears to be updating just fine.
Maybe one of my config changes or permissions changes did not take effect until I rebooted?
This is possible I suppose, or there was a stuck lock file or socket.

Glad to hear it is resolved now