:15 2011] [error] [client 192.168.123.102] Premature
end of script headers: sumo_fastcgi.pl
This is when using the hjksolutions setup linked in my original message.
Thanks.
On 02/13/2011 11:24 AM, Mark Hughes wrote:
I am trying to work through deployng a Catalyst app on an apache2 server
On 02/13/2011 11:46 AM, Francisco Obispo wrote:
Is there a reason why you need it to be fast_cgi and not mod_perl ?
This app is ultimately supposed to go onto a shared server. mod_perl is
not part of the standard setup. I also read that when using mod_perl
code changes required a restart
On 02/13/2011 11:55 AM, Lyle wrote:
On 13/02/2011 18:24, Mark Hughes wrote:
(I think because mod_fcgi breaks on ExternalServer directives.)
mod_fcgid has different directives to mod_fastcgi. When looking at
documentation this can often lead to confusion and a mismatch of the
different
On 02/13/2011 12:36 PM, Aaron Dancygier wrote:
Can you post your Apache config.
--Aaron
Here it is the most recent version of the relevant part. Most is
boilerplate generated by ISPConfig. I've made the marked changes near
the top and commented out the ScriptAlias directive part way down:
On 02/13/2011 02:29 PM, Tomas Doran wrote:
On Feb 13, 2011, at 10:38 AM, Mark Hughes wrote:
I should have added that this is a sample of my error.log:
[root@mayfly log]# cat error.log
[Sun Feb 13 11:29:45 2011] [warn] (104)Connection reset by peer:
mod_fcgid: read data from fastcgi server
On 02/13/2011 02:59 PM, Lyle wrote:
On 13/02/2011 19:51, Mark Hughes wrote:
AddHandler fcgid-script .pl
You have this well before your fcgid config. Might have an effect, can't
say for sure without testing.
I moved that whole location to after the fcgi config section,
restarted everything
On 02/14/2011 01:49 AM, Tomas Doran wrote:
Perhaps there's a permission problem but, in an effort to figure this
out, I have set everything at the site's root, web, to 777 and
everything in the scripts directory to 777, too.
Start apache with one child using strace -f
Watch what's actually
On 02/14/2011 06:42 AM, Nigel Metheringham wrote:
I'd suggest deleting that /tmp/sumo entirely and letting it recreate.
Its probably not really a good idea to have it in /tmp shareable by
different uids either, but to try and get stuff running I'd just zilch
it for now and then work on
