Problem with emailed schedule reports

[tpwebb]

Hello

I am having problems with emailing scheduled reports, the reports are attaching the pdf file but there is no data in them and they are corrupt or unreadable when the email is received.

The reports are working fine and can be downloaded from the web site and appear without issues.

Can you advise how we can fix this?

[benjaminsmith]

Hello @tpwebb,

When there are issues with schedule reports, you'll want to first verify that your have the correct URL settings in your system interface. Go to Admin > System Config > System Settings.

sys-settings.png

If that's correct, then send us your system profile along with the corrupted report for us to review. Thanks.

To send us your system profile.
Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and share this in a private message and then reply to this post to bring it up in the queue.

[tpwebb]

Hello

I have sent the files as requested.

Thansk

[benjaminsmith]

Hello,

Thanks for sending over the system profile. I noticed in the database logs that the XI eventqueue table is corrupted.

190917 20:22:48 [ERROR] /usr/libexec/mysqld: Table './nagiosxi/xi_eventqueue' is marked as crashed and should be repaired
190917 20:22:48 [ERROR] /usr/libexec/mysqld: Table './nagiosxi/xi_eventqueue' is marked as crashed and should be repaired
190917 20:22:48 [ERROR] /usr/libexec/mysqld: Table './nagiosxi/xi_eventqueue' is marked as crashed and should be repaired

Log into as root to the terminal and run the following command:

Code: Select all

/usr/local/nagiosxi/scripts/repair_databases.sh

If the issue persists, please send me the blank report, and then schedule a report to run in the next few minutes, and post the log output from the following tail command.

Code: Select all

tail -f /var/log/httpd/*error_log 

[tpwebb]

Hello

Tail messages

[root@nagios ~]# tail -f /var/log/httpd/*error_log
==> /var/log/httpd/error_log <==
--base: snmpget [email protected]:161::::2:v4only for ifHighSpeed.70 -> 1000 Mb/s
--base: snmpget [email protected]:161::::2:v4only for ifHCInOctets.70 -> 695973562
--base: snmpget [email protected]:161::::2:v4only for ifHighSpeed.72 -> 1000 Mb/s
--base: snmpget [email protected]:161::::2:v4only for ifHCInOctets.72 -> 18627909894663
--base: snmpget [email protected]:161::::2:v4only for ifHighSpeed.74 -> 1000 Mb/s
--base: snmpget [email protected]:161::::2:v4only for ifHCInOctets.74 -> 4894221263
sed: -e expression #1, char 75: unterminated `s' command
--2019-10-19 08:11:29-- https://nagios.metrotraffic.seq.its/nag ... f35eaa79ac
Connecting to 10.79.3.5:3128... connected.
Proxy tunneling failed: Service UnavailableUnable to establish SSL connection.

==> /var/log/httpd/ssl_error_log <==
[Thu Oct 17 15:23:24 2019] [error] [client 10.79.3.16] PHP Notice: Undefined variable: v3_priv_password in /usr/local/nagiosxi/html/includes/configwizards/switch/switch.inc.php on line 1183, referer: https://nagios.metrotraffic.seq.its/nag ... wizard.php
[Thu Oct 17 15:23:24 2019] [error] [client 10.79.3.16] PHP Notice: Undefined variable: v3_priv_proto in /usr/local/nagiosxi/html/includes/configwizards/switch/switch.inc.php on line 1183, referer: https://nagios.metrotraffic.seq.its/nag ... wizard.php
[Fri Oct 18 12:27:04 2019] [error] [client 10.79.3.19] PHP Warning: Unterminated comment starting line 1 in /usr/local/nagiosxi/html/includes/components/actions/actions.inc.php(900) : eval()'d code on line 1, referer: https://nagios.metrotraffic.seq.its/nag ... services=1
[Fri Oct 18 12:27:17 2019] [error] [client 10.79.3.19] PHP Warning: Unterminated comment starting line 1 in /usr/local/nagiosxi/html/includes/components/actions/actions.inc.php(900) : eval()'d code on line 1, referer: https://nagios.metrotraffic.seq.its/nag ... MCH328L201
[Fri Oct 18 12:27:26 2019] [error] [client 10.79.3.19] PHP Warning: Unterminated comment starting line 1 in /usr/local/nagiosxi/html/includes/components/actions/actions.inc.php(900) : eval()'d code on line 1, referer: https://nagios.metrotraffic.seq.its/nag ... MCH328L201
[Fri Oct 18 12:27:35 2019] [error] [client 10.79.3.19] PHP Warning: Unterminated comment starting line 1 in /usr/local/nagiosxi/html/includes/components/actions/actions.inc.php(900) : eval()'d code on line 1, referer: https://nagios.metrotraffic.seq.its/nag ... services=1
[Fri Oct 18 12:27:46 2019] [error] [client 10.79.3.19] PHP Warning: Unterminated comment starting line 1 in /usr/local/nagiosxi/html/includes/components/actions/actions.inc.php(900) : eval()'d code on line 1, referer: https://nagios.metrotraffic.seq.its/nag ... MCH328L201
[Fri Oct 18 12:27:56 2019] [error] [client 10.79.3.19] PHP Warning: Unterminated comment starting line 1 in /usr/local/nagiosxi/html/includes/components/actions/actions.inc.php(900) : eval()'d code on line 1, referer: https://nagios.metrotraffic.seq.its/nag ... MCH328L201
[Sat Oct 19 07:55:05 2019] [error] [client 10.95.3.33] PHP Warning: ldap_bind(): Unable to bind to server: Invalid credentials in /usr/local/nagiosxi/html/includes/components/ldap_ad_integration/adLDAP/src/adLDAP.php on line 714, referer: https://nagios.metrotraffic.seq.its/nag ... f&noauth=1
[Sat Oct 19 07:58:38 2019] [error] [client 10.95.3.33] PHP Warning: Unterminated comment starting line 1 in /usr/local/nagiosxi/html/includes/components/actions/actions.inc.php(900) : eval()'d code on line 1, referer: https://nagios.metrotraffic.seq.its/nag ... w=services

[lmiltchev]

If you are using a proxy, make sure that localhost is excluded as described in the KB article below:

https://support.nagios.com/kb/article/n ... s-147.html

Let us know if this helped. Thanks!

Can you show us a screenshot of the "System Settings" page (Admin > System Config > System Settings)?

[tpwebb]

Thank you,

I had originally followed this document, blindly doing a copy and paste, but sadly did not comment out the https_proxy option as documented.

Once this was done, the reports worked.

This can now be closed.

[scottwilkerson]

Thank you,

I had originally followed this document, blindly doing a copy and paste, but sadly did not comment out the https_proxy option as documented.

Once this was done, the reports worked.

This can now be closed.

Great!

Locking thread