First a brief history: I have been developing a series of 30 plus linked reports. The development environment is OSX. The development test environment is OSX.
All seems to have gone well with respect to wkhtmltopdf. I have followed the threads reporting performance issues. I have not experienced any, except for my largest test report, a 30 page page-view report, seemed to produce a rather large 15.5 MB pdf file. This could take a little time to download from the server.
We have just configured a Linux QC server. wkhtmltopdf is installed and appears to be working fine. Remarkably, the resulting pdf files are substantially smaller. For example, a 941 kb OSX file was 33 kb on the Linux server. A 285 kb OSX file containing ChartDirector graphics became a 40 kb Linux file. I'm guessing this is a font issue on the OSX systems.
In my initial testing of the Linux system all reports were running fine. Then I tried exporting to PDF. Everything ran fine except the report that produced the 30 page, 15.5 MB file. It just hung. On the OSX system, it took about two and one half minutes to run, most of the time was spent downloading across the network. Locally it to 15 seconds to run and display the PDF.
On the Linux system it never did complete. I finally received a 500 Internal Server Error. The server encountered an internal error or misconfiguration and was unable to complete your request.
This report has no problem with smaller datasets, say a two page report.
Remember, the problem only appears on a twenty or thirty page report. That amounts to less than 50 rows from the primary table for the 30 page report. A number of tables are joined to bring the report together. It runs quickly when producing HTML.
So, I edited the report code to turn export debug on. When I ran the problem report, it completed very quickly and gave me the wkhtmltopdf command line to test it out.
I logged into the Linux server and ran the command line, directing the output to a file. It ran so fast I was sure there was a problem...maybe less than a second. When I opened the resulting PDF, it was fine. The only difference I noticed was formatting of the header timestamp. So I know the HTML is fine and wkhtmltopdf can translate it without a problem. BTW, the Linux PDF file for this particular test is 137 KB as opposed to 13.9 MB OSX file.
Next I tried the command: ps -ef | grep dbr I was surprised to find a number of processes out there from the last two days:
/usr/bin/php /home/mydomain/public_html/mydbr/report.php
/usr/local/bin/wkhtmltopdf -q -s LETTER -O Landscape --header-html http://mydomain.com/mydbr/user/export_header_pdf.php --margin-top 13 /tmp/1508430776.html -
/usr/bin/php /home/mydomain/public_html/mydbr/report.php
/usr/bin/php /home/mydomain/public_html/mydbr/report.php
grep --color dbr
/usr/bin/php /home/mydomain/public_html/mydbr/report.php
/usr/local/bin/wkhtmltopdf -q -s LETTER -O Landscape --header-html http://mydomain.com/mydbr/user/export_header_pdf.php --margin-top 13 /tmp/1162373632.html -
/usr/bin/php /home/mydomain/public_html/mydbr/report.php
/usr/bin/php /home/mydomain/public_html/mydbr/index.php
/usr/bin/php /home/mydomain/public_html/mydbr/index.php
/usr/bin/php /home/mydomain/public_html/mydbr/report.php
/usr/local/bin/wkhtmltopdf -q -s LETTER -O Landscape --header-html http://mydomain.com/mydbr/user/export_header_pdf.php --margin-top 13 /tmp/1187638306.html -
/usr/bin/php /home/mydomain/public_html/mydbr/report.php
/usr/bin/php /home/mydomain/public_html/mydbr/report.php
/usr/local/bin/wkhtmltopdf -q -s LETTER -O Landscape --header-html http://mydomain.com/mydbr/user/export_header_pdf.php --margin-top 13 /tmp/2003766335.html -
So there appears to be some issue with the myDBR interface to wkhtmltopdf that I don't know how to chase down.
This problem is on myDBR 3.6.0 (build 1691). I just updated to myDBR 3.6.0 (build 1694) and can confirm this is still an issue.
Can anyone suggest a course of action to track this down and correct it?
