Re: Not your normal " Premature end of script headers:"

When you say "Carp", do you mean Carp or do you mean CGI::Carp? Since this is CGI, you may want:

use CGI::Carp qw( fatalsToBrowser );
[download]

This gives you the error through the server that ends up in your browser, if it can, instead of through your log files. It's a nice, quick tool to use when debugging this sort of thing. It takes care of putting out headers for itself and everything.

Comment on Re: Not your normal " Premature end of script headers:" Download Code

Replies are listed 'Best First'.
Re^2: Not your normal " Premature end of script headers:" by yegg (Acolyte) on Jun 18, 2008 at 17:04 UTC
I meant CGI::Carp, and when I did what you suggest, no more additional error information printed out. Does this tell you anything? I would guess it indicates the script is never even executed.	[reply]
Re^3: Not your normal " Premature end of script headers:" by mr_mischief (Monsignor) on Jun 18, 2008 at 17:17 UTC
It could mean it's never executed. That could be due to path issues with the perl program (unlikely, since it works up to that point). It could be due to child program limits or the web server user's process limit. It could be due to a memory limit on the web server process and its children or the web server user. It could mean something, somewhere, is causing a syntax error (unlikely, since it works initially). If it happens around the same time of day, it could be due to time range issues in your ACLs (which is also unlikely, since you say restarting the server works no matter when it happens). It could mean the CGI program is running but unable to open a file handle for its STDIN to get info from the server or STDOUT to get information back to the server due to file handle limits. It's a good idea to know about how many file handles the web server user has open, how much memory all the processes it runs are using, and how many processes it has running when this happens. Then, compare that to the mechanism which limits those things. It's ulimit on Unixy systems; I don't remember the name of the policy mechanism that handles such things on Windows.	[reply]
Re^4: Not your normal " Premature end of script headers:" by yegg (Acolyte) on Jun 18, 2008 at 19:03 UTC
Thanks. It doesn't happen at a particular time of day, just some time after the restart. I'm not sure where the limit mechanisms are in Windows either, but I'll find out. (I'm used to unix as well). As for the resources used, see my other reply I just made for values for in this state and right after a restart.	[reply]