Re: [Catalyst] Help Deploying on mod-fcgi Rather than mod_fastcgi

2011-02-13 Thread Mark Hughes
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 error. [Sun Feb 13 11:29:45 2011] [error] [client 192.168.123.102] Premature end of script

Re: [Catalyst] Help Deploying on mod-fcgi Rather than mod_fastcgi

2011-02-13 Thread Francisco Obispo
Is there a reason why you need it to be fast_cgi and not mod_perl ? 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:

Re: [Catalyst] Help Deploying on mod-fcgi Rather than mod_fastcgi

2011-02-13 Thread Lyle
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 directives. The directives you should be

Re: [Catalyst] Help Deploying on mod-fcgi Rather than mod_fastcgi

2011-02-13 Thread Mark Hughes
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

Re: [Catalyst] Help Deploying on mod-fcgi Rather than mod_fastcgi

2011-02-13 Thread Aaron Dancygier
Can you post your Apache config. --Aaron On Sun, 13 Feb 2011 11:38:08 -0700, Mark Hughes mhug...@law.du.edu 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

Re: [Catalyst] Help Deploying on mod-fcgi Rather than mod_fastcgi

2011-02-13 Thread Mark Hughes
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

Re: [Catalyst] Help Deploying on mod-fcgi Rather than mod_fastcgi

2011-02-13 Thread Mark Hughes
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:

Re: [Catalyst] Help Deploying on mod-fcgi Rather than mod_fastcgi

2011-02-13 Thread Tomas Doran
On 13 Feb 2011, at 18:46, Francisco Obispo wrote: Is there a reason why you need it to be fast_cgi and not mod_perl ? 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]

Re: [Catalyst] Help Deploying on mod-fcgi Rather than mod_fastcgi

2011-02-13 Thread Lyle
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. Lyle ___ List: Catalyst@lists.scsys.co.uk Listinfo:

Re: [Catalyst] Help Deploying on mod-fcgi Rather than mod_fastcgi

2011-02-13 Thread Mark Hughes
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

Re: [Catalyst] Help Deploying on mod-fcgi Rather than mod_fastcgi

2011-02-13 Thread Mark Hughes
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,