Page 1 of 1
Pdf Scheduled reports corrupt
Posted: Thu Apr 04, 2013 9:02 am
by arnab.roy
Hi Guys,
I think a lot of us have posted this, I can see a post by benhank here which basically speaks about the same issue, basically the pdf file attached to any scheduled report is corrupt is generating garbage attachments to the report email. I am attaching an example (This forum wont let me attach guess what was the reason the uploaded file was empty so true!!!

).
We are running XI Version 2012R1.6
Re: Pdf Scheduled reports corrupt
Posted: Thu Apr 04, 2013 9:37 am
by abrist
Do a running tail on the httpd error_log and then try to open a report from the XI ui. Post the output of the tail here.
Are the reports empty or corrupt?
Re: Pdf Scheduled reports corrupt
Posted: Thu Apr 04, 2013 9:47 am
by arnab.roy
I think its generating an empty file of size zero bytes. On looking at this I think this is due to having ssl with self signed cert.
[Thu Apr 04 15:45:24 2013] [error] [client 172.20.0.123] PHP Notice: Undefined index: privacy_policy_url in /usr/local/nagiosxi/html/includes/header.inc.php on line 202
--2013-04-04 15:45:39--
https://localhost/nagiosxi/reports/avai ... s&mode=pdf
Resolving localhost... 127.0.0.1
Connecting to localhost|127.0.0.1|:443... connected.
ERROR: cannot verify localhost's certificate, issued by `/C=GB/ST=Hampshire/L=Fleet/O=Khipu-Networks, Ltd/OU=Technical/CN=karma.khipu-networks.com/emailAddress=
[email protected]':
Self-signed certificate encountered.
ERROR: certificate common name `karma.khipu-networks.com' doesn't match requested host name `localhost'.
To connect to localhost insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
[Thu Apr 04 15:45:39 2013] [error] [client 172.20.0.123] PHP Notice: Undefined variable: cmd in /usr/local/nagiosxi/html/includes/components/scheduledreporting/schedulereport.php on line 202, referer:
http://karma.khipu-networks.com/karma/i ... &id=hoagj6
Re: Pdf Scheduled reports corrupt
Posted: Thu Apr 04, 2013 10:01 am
by lmiltchev
arnab.roy,
I filed an internal bug report on the issue. We will let you know when we find a possible solution. Thanks!