PDF Stamper – Download links leading to 503 pages

[morley]

We have recently switched hosts; here are the new host’s specs:

cPanel Version 11.34.1 (build 12)

Theme x3

Apache version 2.2.23

PHP version 5.3.22

MySQL version 5.5.30-cll

Architecture x86_64

Operating system linux

Path to sendmail /usr/sbin/sendmail

Path to Perl /usr/bin/perl

Perl version 5.10.1

Kernel version 2.6.32-379.14.1.lve1.1.9.9.el6.x86_64

cPanel Pro 1.0 (RC1)

Here are our plugin versions:

WP eStore v6.9.6.4

WP PDF Stamper v4.2.2

The host uses Litespeed. We haven’t experienced this problem with either of our previous hosts, so I’m thinking it must be some kind of configuration issue. When a user clicks on his links, he gets a 503 error page which says “The server is temporarily busy, try again later!” I was provided with the log below, and was told the following:

We run the latest version of PHP – 5.3.22 at this time. It is entirely possible there is a bug in the latest version of PHP that is affecting you but it’s also quite likely the script isn’t 100% compatible with some nuance of this version.

013-03-08 18:48:31.186 [INFO] [208.47.134.46:40319-0#APVH_cambridgelsat.com] connection to [/tmp/lshttpd/APVH_cambridgelsat.com_Suphp.sock] on request #0, confirmed, 1, associated process: 721791, running: 1, error: Connection reset by peer!

2013-03-08 18:48:32.750 [INFO] [208.47.134.46:40319-0#APVH_cambridgelsat.com] connection to [/tmp/lshttpd/APVH_cambridgelsat.com_Suphp.sock] on request #0, confirmed, 1, associated process: 721857, running: 1, error: Connection reset by peer!

2013-03-08 18:48:32.750 [NOTICE] [208.47.134.46:40319-0#APVH_cambridgelsat.com] Max retries has been reached, 503!

2013-03-08 18:48:32.750 [NOTICE] [208.47.134.46:40319-0#APVH_cambridgelsat.com] oops! 503 Service Unavailable

Because the process is being attempted multiple times, any time a link is clicked, its access limit is maxed out immediately.

[morley]

I did some more testing and turned on the debug logs. In looking at the log, it’s getting stuck at the stamping step:

[03/09/2013 5:57 AM] – SUCCESS :Attempting to stamp the PDF file using the internal stamping API. PDF Stamper version: 4.2.2

We have set the plugin to stamp at the time of download. The host has the PHP limit set to 128M, and the files are around 35 pages long, so that would seem to rule out a RAM shortage. The problem doesn’t occur every time however (occasionally, the files will get stamped and download properly), so I’m not sure. Any ideas as to what’s happening here?

[wzp]

Please enable the eStore debug logs, and generate a download link. After attempting to use the link, please check the download_manager_debug.log file.

Also, please provide +/-3 lines from that stamping attempt log extract in your last post, along with the name of the log file (because there are many log files).

Also, do you have problems only with stamped files?

[morley]

See below for the log files. The top one is “eStore_post_payment_debug.log” and the bottom one is “download_manager_debug.log” As you can see, some of the files were stamped successfully while others were not.

We only sell stamped files, and the problem seems to be with the stamping itself. Thanks.

[admin deleted debug log after checking]

[admin]

Thank you for the debug. The plugin is working fine. Your new server needs more resource/power. There is no magic to it… stamping a PDF file dynamically is resource (CPU and RAM) intensive. If you have enabled the optional file encryption feature then it takes even more resource to stamp the file. The amount of resource it requires depends on a few things, for example:

– How big a particular file is

– The complexity of the content

– If extra encryption is needed or not

– etc.

When the stamper is doing an stamping operation, if it reaches the maximum resource allocation of your server, your server’s restriction will kill the script and hence the stamping fails. Another thing to remember is that your server has other loads from your visitors on the site. So at any given time how much load your server has from other operations also plays a factor. The only way to ensure that an stamping will work all the time is to have more resource available than what you need at maximum server load.

[Author]

Posts