Page 1 of 1
5.4.12 Upgrade breaks forced immediate checks - GUI
Posted: Fri Jan 26, 2018 9:51 am
by sonyfreek
We have upgraded two servers to 5.4.12 two days ago and have seen that the Forced immediate checks on services and hosts is no longer working properly. When executing a forced immediate check, the check times out with the message "Your request was not processed in a timely manner. It may still execute, as the server may be temporarily busy." Executing this same check via the CLI provides immediate response.
While running the forced immediate check, I have monitored the /var/log/messages file to determine if there were any errors generated, but none were seen. Are there better logs to monitor for this and does Nagios know about and have a resolution to this problem?
Re: 5.4.12 Upgrade breaks forced immediate checks - GUI
Posted: Fri Jan 26, 2018 10:53 am
by sonyfreek
We've also noticed that the system is no longer applying the configuration changes. I enabled a previously inactive service for testing purposes and the apply has taken over 10 minutes without success (or failure). It's just filling up my screen with .'s The same happens on both hosts that were upgraded.
Re: 5.4.12 Upgrade breaks forced immediate checks - GUI
Posted: Fri Jan 26, 2018 12:21 pm
by dwhitfield
Can you post your
/tmp/nagiosxi/upgrade.log?
Also, can you PM me your Profile? You can download it by going to Admin > System Config > System Profile and click the ***Download Profile*** button towards the top. If for whatever reason you *cannot* download the profile, please put the output of View System Info (5.3.4+, Show Profile if older) in the thread (that will at least get us some info). This will give us access to many of the logs we would otherwise ask for individually. If security is a concern, you can unzip the profile take out what you like, and then zip it up again. We may end up needing something you remove, but we can ask for that specifically.
You can also generate a profile manually using the script at /usr/local/nagiosxi/html/includes/components/profile/getprofile.sh
That should generate a profile in /usr/local/nagiosxi/var/components/ which you can get off the server with an application such as FileZilla.
After you PM the profile, please update this thread. Updating this thread is the only way for it to show back up on our dashboard.
If you get an error that PROFILE BUILD FAILED, please see
https://support.nagios.com/kb/article.p ... ategory=44
UPDATE: Profile received and shared with techs
Re: 5.4.12 Upgrade breaks forced immediate checks - GUI
Posted: Fri Jan 26, 2018 1:25 pm
by sonyfreek
I've PM'd the system profile and am working on getting the update.log
Thanks,
Wayne
Re: 5.4.12 Upgrade breaks forced immediate checks - GUI
Posted: Fri Jan 26, 2018 3:23 pm
by dwhitfield
We've seen another user with similar symptoms after upgrade. For now, I would suggest rolling back to 5.4.11. We hope to have a fix out in XI 5.5 (or possibly 5.4.13).
Re: 5.4.12 Upgrade breaks forced immediate checks - GUI
Posted: Fri Jan 26, 2018 3:53 pm
by sonyfreek
Thank you. We've rolled back to the previous version.
Re: 5.4.12 Upgrade breaks forced immediate checks - GUI
Posted: Fri Jan 26, 2018 4:16 pm
by dwhitfield
As of right now, it doesn't seem like a 5.4.13 is likely. 5.5 is scheduled for March, but could be pushed back.
Were you hitting any specific bugs that were fixed in 5.4.12?
Re: 5.4.12 Upgrade breaks forced immediate checks - GUI
Posted: Sun Jan 28, 2018 9:22 am
by sonyfreek
The primary reason we upgraded was due to the NagiosQR vulnerability, not because of any of the other bugs.
Sincerely,
Wayne
Re: 5.4.12 Upgrade breaks forced immediate checks - GUI
Posted: Mon Jan 29, 2018 12:44 pm
by kyang
Did you mean NagiosQL?
Which vulnerability?
If the restore of 5.4.11 is working for you did you have any more questions?
Re: 5.4.12 Upgrade breaks forced immediate checks - GUI
Posted: Tue Jan 30, 2018 2:56 pm
by dwhitfield
kyang wrote:
Which vulnerability?
I assume this one:
Code: Select all
Fixed vulnerability in NagiosQL (Thanks @iotennui, @BennyHusted, @0xC413 on twitter) -JO,TM