New NagiosXI server apply configuration taking hours

[akepley]

I haven't seen any new jobs start for php in the last 10 minutes, but the jobs that were running are still running (132 php processes). Should I reboot the server to get a clean start?

[avandemore]

Sure, if that doesn't upset your environment that is the cleanest way to ensure good operation and start up.

[akepley]

This is still setup for the new production server, so we're still using our old server until I get the bugs out of this one. I'll reboot.

[akepley]

Since restart almost an hour ago, only 12 php processes currently. So this seems like a good fix. Any idea what caused the issues in the database?

[akepley]

Ok, so php processes are fine now and hopefully we won't see a memory leak.

I still have the issue with the apply configuration showing successful, writing to the configs, but when viewing the service in core config manager, it still shows as Not Applied and the service detail is also not showing the updated config.

[avandemore]

I don't have a reason for how your system got into that state, but it's not something that happens under normal conditions.

What is the output of:

Code: Select all

grep "date.timezone" /etc/php.ini
ls -l /etc/localtime
php -r 'echo date("D M j G:i:s T Y")."\n";'
date
mysql -unagiosxi -pn@gweb -e "SELECT NOW();"

[akepley]

The MySQL database is in RDS which defaults to UTC. You want me to match it with the NagiosXI server?

[avandemore]

Yes, they need to be in sync. Normally this can be accomplished by toggling timezones in XI > Admin, but I'm not sure if that would work in your case.

[akepley]

Making the change now. I've got some more changes to make in core config so I'll wait until this is complete before making those changes and testing.

Thanks!

[akepley]

Hey, found something else! This is more toward my post last week about import configs, but that thread is locked and since we're talking about apply configs, I guess I'll put it here. When deleting services, I get the dependent relationships failures. That's not a problem, the problem is that my service escalations from the import have terrible names. See below.

Is this normal for imported service escalations/host escalations? This is really tricky to find specific escalations that were named by host in the prior nagiosxi server, but have these random strings in the new.