Scheduled report not working again

[BenCowan]

Nagios XI 2024R1.3 RHEL 9

We send out a daily report to management. Since upgrading to 1.3 the email attached pdf opens with the following:

This site can’t be reached
Check if there is a typo in nagios.scs.nevada.edunagiosxi.
DNS_PROBE_FINISHED_NXDOMAIN

The only error I've found so far is in the chromium_report.log:
Fontconfig error: Cannot load default config file: No such file: (null)

[danderson]

Thanks for reaching out @BenCowan,

What do you see in /usr/local/nagiosxi/var/scheduledreporting.log? The backend reporting system is not able to access the URL. Normally it should try to access localhost and always work but perhaps something changed.

[BenCowan]

Looks normal to me, but will post here...

DEBUG:
[11-05-2024 06:39:20] Message sent! (method=sendmail), Referer: includes/components/scheduledrepo rting > Scheduled Report

DELETING /usr/local/nagiosxi/tmp/scheduledreport-bcowan-FtFBsS4OYsQu-1730817558-Alerts - Last 24 Hours.pdf
FREQ: Daily<BR>[Tue, 05 Nov 2024 07:30:04 -0800] EMAIL: Array
(
[to] => scs_operational_managers@nshe.nevada.edu, ns_all@nshe.nevada.edu, se_sysnotify@nshe.n evada.edu, ias_dba@nshe.nevada.edu, ias_psa@nshe.nevada.edu
[subject] => Nagios Alerts - Last 24 Hours
[attachment] => Array
(
[0] => Array
(
[0] => /usr/local/nagiosxi/tmp/scheduledreport-bcowan-FtFBsS4OYsQu-1730820602 -Alerts - Last 24 Hours.pdf
[1] => 1730820602-Alerts - Last 24 Hours.pdf
)

)

[message] => This scheduled report was automatically generated by Nagios XI and sent to you a s requested by bcowan (Ben Cowan).

Good Morning,

The Nagios report on Alerts received in the last 24 hours has been attached as a pdf.

Regards,

Ben Cowan

You can directly access this report at:
https://nagios.scs.nevada.edu/nagiosxi/ ... i%2Fsummar y.php%3Freport%3D1%26displaytype%3D1%26timeperiod%3Dlast24hours%26smon%3D6%26sday%3D1%26syear%3D2 023%26shour%3D0%26smin%3D0%26ssec%3D0%26emon%3D6%26eday%3D10%26eyear%3D2050%26ehour%3D24%26emin%3 D0%26esec%3D0%26hostgroup%3Dall%26servicegroup%3Dall%26host%3Dall%26alerttypes%3D3%26statetypes%3 D2%26hoststates%3D7%26servicestates%3D120%26limit%3D999

Access Nagios XI at:
https://nagios.scs.nevada.edu/nagiosxi/
)

[Tue, 05 Nov 2024 07:30:04 -0800] DEBUG: [11-05-2024 07:30:04] Message sent! (method=sendmail), R eferer: includes/components/scheduledreporting > Scheduled Report

[danderson]

When you go into the Scheduled reporting menu, Reports -> My Scheduled Reports, and you click the edit icon. Is the "Page URL" a full URL or a relative URL? If it's a full URL, you can either change it to a relative URL (I think you would have to make a new report to do this) or you can add the XI domain name to the `/etc/hosts` file.

If it's a relative URL and you are still getting this issue, let me know.

[BenCowan]

It's a relative url:

includes/components/nagioscore/ui/summary.php?report=1&displaytype=1&timeperiod=last24hours&smon=6&sday=1&syear=2023&shour=0&smin=0&ssec=0&emon=6&eday=10&eyear=2050&ehour=24&emin=0&esec=0&hostgroup=all&servicegroup=all&host=all&alerttypes=3&statetypes=2&hoststates=7&servicestates=120&limit=999

[BenCowan]

Upgraded to Nagios XI 2024R1.3.1 RHEL 9

Still have the same problem

[danderson]

The issue is probably that the XI machine is having trouble resolving the domain nagios.scs.nevada.edu to itself. I'm curious if you could just add that domain to the /etc/hosts file on the XI machine. Do you have anything special configured with apache? Maybe some proxy settings or something.

I'm trying to replicate the issue that you are seeing but I'm having a hard time doing so. I'm trying to get the report to try to reach out to the external url specified in the system settings page but I always get it reaching out to localhost.

[BenCowan]

This can be closed out.

The problem turned out to be some rewrite rules we had in the httpd server for port 80. It was fubar-ing the url whenever the server was 'localhost', which is what the scheduled report was doing. This rule had been in place for several months with no problem, so I'm not sure exactly what changed. I'm assuming it happened during routine patching.

Sorry for the goose chase.

[gwesterman]

I'm glad you found the solution. Locking this thread.