PDF Report(s) Corrupt When Emailed

[ssunga]

Hey @RobMcL,

Did you configure the scheduled report to include a JPEG report? If you did, you might have to go into the scheduled report interface, click 'edit' on the report, and then click the save button. The JPEG reports were removed (so you won't even see the option) and it's possible it's causing issues.

Please let us know if that helps.

[RobMcL]

No, I didn't have it configured to include a JPEG report, but just for posterity purposes I edited the report and saved it again. Still having the issue.

I also was able to get my Nagios XI upgraded to 2024R1.1.3 after opening a support case so now I'm running the latest version. Didn't help either

[ssunga]

Hmm, that's unfortunate.

Your chromium.log is empty - can you check that you have chromium installed?

If you don't this might resolve the issue altogether:

- Check that chromium is installed
- If it's not, you can install it on RHEL 9 by just running

yum install chromium chromium-headless

[RobMcL]

I do have Chromium installed and it upgraded when I ran that command:

sudo yum install chromium chromium-headless
Last metadata expiration check: 1:11:57 ago on Thu 06 Jun 2024 10:04:59 AM EDT.
Package chromium-123.0.6312.105-1.el9.x86_64 is already installed.
Package chromium-headless-123.0.6312.105-1.el9.x86_64 is already installed.
Dependencies resolved.
========================================================================================================================
Package Architecture Version Repository Size
========================================================================================================================
Upgrading:
chromium x86_64 125.0.6422.141-1.el9 epel 88 M
chromium-common x86_64 125.0.6422.141-1.el9 epel 14 M
chromium-headless x86_64 125.0.6422.141-1.el9 epel 55 M

Transaction Summary
========================================================================================================================
Upgrade 3 Packages

I don't think I was clear previously about the chromium log, I do have a log, but when I try to run the report it doesn't send anything to the log. I have this in the log though when an report ran on Monday. It doesn't send anything to this log when I ad-hoc run the report:

Code: Select all

[Mon, 03 Jun 2024 09:00:30 +0000] HOME=/usr/local/nagiosxi/tmp chromium-browser --headless=new --ignore-certificate-errors --enable-low-end-device-mode --disable-gpu --virtual-time-budget=10000 --run-all-compositor-stages-before-draw --no-pdf-header-footer --desktop-window-1080p --print-to-pdf='/usr/local/nagiosxi/tmp/topalertproducers-665d862eb128f.pdf' 'http://localhost/nagiosxi/reports/topalertproducers.php?host=&service=&reportperiod=lastmonth&startdate=&enddate=&hostgroup=&servicegroup=Server+Memory+Utilization&hostservice=services&statetype=hard&state=warning&mode=getreport&token=7cf4c18c47b64f9ffd9704941d0c9720f3a3c067&locale=en_US&records=100000&hideoptions=1&export=1&old_browser_compat=1'
[3821839:3821890:0603/050034.699795:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3821839:3821890:0603/050034.700062:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3821839:3821890:0603/050034.700084:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3821839:3821890:0603/050034.700097:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3821839:3821839:0603/050034.877619:ERROR:policy_logger.cc(157)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build.
[3821839:3821890:0603/050034.906302:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3821839:3821890:0603/050034.906386:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
46004 bytes written to file /usr/local/nagiosxi/tmp/topalertproducers-665d862eb128f.pdf

[rj-admin2]

Hi,

It turns out the issue was incorrect permissions against the reports logging file. Also both the Internal and External URL configuration MUST be identical.

TIA.

[RobMcL]

I'm still having this issue. My Internal URL is set correctly, but my External URL is blank (as it says it should be if it's not different).

@rj-admin2,

Curious, what specific permissions you changed/fixed on what specific logging file.

@ssunga / @swolf,

Any other ideas? Should I just be opening a support case on this? My CTO is looking for these reports and I don't want to have to manually export them from the console every month. Thanks!

[ssunga]

Hey @RobCL

At this point I would suggest opening a support call. https://answerhub.nagios.com/support/s/

[rj-admin2]

Hey @RobCL

My external URL was blank to begin with too. I had to make it exactly the same as the internal URL. Then:

The permissions need to be updated on the scheduled reporting log file so run the following as root to do that.

chown nagios.nagios /usr/local/nagiosxi/var/scheduledreporting.log

chmod 666 /usr/local/nagiosxi/var/scheduledreporting.log

This cured it for me.

TIA.

[jmichaelson]

@RobCL, can you try making the external and internal URL's match? It might save you a support call.

[RobMcL]

@ssunga
@rj-admin2
@jmichaelson

Wow, matching the External URL WAS the fix. I'm stunned it was that, but thankful it was such an 'easy fix'. Perhaps the documentation / help section of that portion should be updated, OR whatever code is relying on it be adjusted.

THANKS EVERYONE!