Page 1 of 2
after upgrade to 5.5.1 wkhtmltox reports failed
Posted: Thu Aug 09, 2018 1:53 am
by scharft
Hi,
normally we use wkhtmltox to send all our reports that are created by our report user.
After we upgraded nagios xi to version 5.5.1 its not possible. In every mail we see the logon screen.
i have attached a file with screenhots from the last successful and the first failed report for better understanding.
best Regards
Re: after upgrade to 5.5.1 wkhtmltox reports failed
Posted: Thu Aug 09, 2018 10:33 am
by lmiltchev
Are you using SSL? What is the version of wkhtmltox that you are currently using?
Run the following command and show the output:
Note: There was a bug with wkhtmltox (not working properly with SSL), so in Nagios XI 5.5.2, we needed to downgrade the wkhtmltox's version. For some reason, I don't see the bugfix in the changelog, however I see the following section in the "/tmp/nagiosxi/upgrade" script:
Code: Select all
# Downgrade wkhtmltox to version that works properly with SSL
echo "Fixing wkhtmltox version..."
if [ `command -v yum` ]; then
if rpm -q wkhtmltox >/dev/null; then
rpm -e wkhtmltox
fi
fi
(
cd ./subcomponents/wkhtmltox
./install
)
You can try upgrading the Nagios XI to 5.5.2 to see if this is going to fix your issue. Let us know if this helped. Thank you!
Re: after upgrade to 5.5.1 wkhtmltox reports failed
Posted: Mon Aug 13, 2018 6:30 am
by scharft
hi,
i've updated to nagios 5.5.2 but it doesn't help.
the version is: wkhtmltox-0.12.1.3-1~centos7.x86_64
any suggestions?
best Regards
Re: after upgrade to 5.5.1 wkhtmltox reports failed
Posted: Mon Aug 13, 2018 7:17 am
by jomann
When you say you're using wkhtmltox to send reports do you mean you are using scheduled reporting from inside of Nagios XI?
Re: after upgrade to 5.5.1 wkhtmltox reports failed
Posted: Tue Aug 14, 2018 2:00 am
by scharft
yes, you can see it in the screenshots of microsoft oulook mails in the beginning of this threat.
Re: after upgrade to 5.5.1 wkhtmltox reports failed
Posted: Tue Aug 14, 2018 2:23 pm
by tgriep
The account that setup the scheduled reports, is is an admin account to a user account?
If it is a user account, what are the permission settings?
Can you run the report manually in the XI interface while logged in as that user and does it display correctly?
When the report is scheduled to run, do you see any errors in the Apache error log files in the /var/log/httpd folder?
If so, can you post the errors here?
Re: after upgrade to 5.5.1 wkhtmltox reports failed
Posted: Fri Aug 24, 2018 12:29 am
by scharft
Hi,
yes the user has admin permission. For the reports we have created an own user named "nagiosreport".
Run the reports manually in the interface works very well and the reports is displayed correctly.
i have attached the error log.
best regards
Re: after upgrade to 5.5.1 wkhtmltox reports failed
Posted: Fri Aug 24, 2018 10:19 am
by tgriep
I am guessing that the report is actually a scheduled page with the information on it, correct?
To see this, login to the XI GUI as that user and go to the Reports > My Scheduled Reports menu and the Type field should say "Page".
If so, the new security settings may have reset the Auto Login for that account so it can be viewed without logging in.
To enable that, go to the Admin > Automatic Login menu, select the user account and enable it.
Then see if the next time the report is ran, it allows you to login automatically and view it in the Email Client you are using.
Re: after upgrade to 5.5.1 wkhtmltox reports failed
Posted: Sun Sep 02, 2018 9:59 am
by scharft
hi,
the autologin is the wrong way because the user for the report has admin permission and btw. to set the autolgin don't work.
In case of emergency and globaly reporting that has negative impact now in the second destination i have to open an ticket to fix the issue asap.
best Regards
Re: after upgrade to 5.5.1 wkhtmltox reports failed
Posted: Tue Sep 04, 2018 9:06 am
by tgriep
If you want to move this to a ticket, that is OK.
With the new version of XI there are a lot of security enhancements done which is probably blocking the report.
The old system brought you to the server and if the user account login credentials were cached, the report would display for you.
The new system doesn't do that so you will have to bypass the security settings to get the same functionality.
Or, you can recreate the report and send it as a jpg or pdf file and then they can be opened and viewed as an attachment.