Mailing List Archive: Apache: Dev

mod_fcgid: settings needed in every vhost?

Index | Next | Previous | View Threaded

walterheck at gmail

Oct 4, 2009, 3:58 PM

Post #1 of 7 (316 views)
Permalink

mod_fcgid: settings needed in every vhost?

Hi Guys,

I am using apache2, php5 and mod_fcgid on CentOS and I'm having a lot
of issues with 500 errors. I came across this blog post:
http://jay.vox.com/library/post/mod_fcgid-ignoring-fastcgi-config-settings.html

I was wondering if that is completely true? And if it is, why is it
that way? Just looking for some answers, trying to understand what is
going on :)

Thanks in advance!

Walter

=== my config ===
[root[at]web01 ~]# yum list installed | grep php
php.x86_64 5.2.9-2.el5.centos installed
[root[at]web01 ~]# yum list installed | grep httpd
httpd.x86_64 2.2.8-1.el5s2.centos installed
[root[at]web01 ~]# yum list installed | grep fcgid
mod_fcgid.x86_64 2.2-4.el5.kb installed

trawick at gmail

Oct 4, 2009, 4:09 PM

Post #2 of 7 (295 views)
Permalink

Re: mod_fcgid: settings needed in every vhost? [In reply to]

On Sun, Oct 4, 2009 at 6:58 PM, Walter Heck <walterheck[at]gmail.com> wrote:

> Hi Guys,
>
> I am using apache2, php5 and mod_fcgid on CentOS and I'm having a lot
> of issues with 500 errors. I came across this blog post:
>
> http://jay.vox.com/library/post/mod_fcgid-ignoring-fastcgi-config-settings.html
>
> I was wondering if that is completely true? And if it is, why is it
> that way? Just looking for some answers, trying to understand what is
> going on :)
>

That's fixed in the mod_fcgid in Subversion. See the "Get It!" information
at http://httpd.apache.org/mod_fcgid/ for how to check out from Subversion.
That particular issue wasn't fixed in the 2.3.1 beta. Hopefully we'll have
another beta out within the next week, and we can use help testing it.

Previously, server config settings had an interesting property. If you only
set them at global scope, they applied to virtual hosts too. But once you
configured one mod_fcgid directive in the vhost the other fcgid settings
would revert to their defaults for that virtual host. (The same was true
for per-directory settings.)

(If you want help here you need to use the ASF-distributed mod_fcgid, not
the now-ancient mod_fcgid 2.2.)

walterheck at gmail

Oct 4, 2009, 4:31 PM

Post #3 of 7 (293 views)
Permalink

Re: mod_fcgid: settings needed in every vhost? [In reply to]

Hi Jeff,

thanks for the quick response!

On Mon, Oct 5, 2009 at 06:09, Jeff Trawick <trawick[at]gmail.com> wrote:
> That's fixed in the mod_fcgid in Subversion. See the "Get It!" information
> at http://httpd.apache.org/mod_fcgid/ for how to check out from Subversion.
> That particular issue wasn't fixed in the 2.3.1 beta. Hopefully we'll have
> another beta out within the next week, and we can use help testing it.
Wait, you say it was fixed and two lines later that it wasn't fixed?
Are you talking about the two different issues of the 500 errors and
the conf per vhost, or am i misunderstanding you? :)

> Previously, server config settings had an interesting property. If you only
> set them at global scope, they applied to virtual hosts too. But once you
> configured one mod_fcgid directive in the vhost the other fcgid settings
> would revert to their defaults for that virtual host. (The same was true
> for per-directory settings.)
So if I fix that in my config, I should be fine?

> (If you want help here you need to use the ASF-distributed mod_fcgid, not
> the now-ancient mod_fcgid 2.2.)
Not a big fan of self-compiled stuff on production systems. I presume
there is no RHEL5 rpm yet? Is anybody on this list sitting on one by
any chance?

kind regards,

Walter

trawick at gmail

Oct 4, 2009, 5:00 PM

Post #4 of 7 (291 views)
Permalink

Re: mod_fcgid: settings needed in every vhost? [In reply to]

On Sun, Oct 4, 2009 at 7:31 PM, Walter Heck <walterheck[at]gmail.com> wrote:

> Hi Jeff,
>
> thanks for the quick response!
>
> On Mon, Oct 5, 2009 at 06:09, Jeff Trawick <trawick[at]gmail.com> wrote:
> > That's fixed in the mod_fcgid in Subversion. See the "Get It!"
> information
> > at http://httpd.apache.org/mod_fcgid/ for how to check out from
> Subversion.
> > That particular issue wasn't fixed in the 2.3.1 beta. Hopefully we'll
> have
> > another beta out within the next week, and we can use help testing it.
> Wait, you say it was fixed and two lines later that it wasn't fixed?
>

I refer to two levels of code:

i. 2.3.1 beta - the issue is not fixed here (level of code in the beta is a
little too old to have that fix)
ii. Subversion (i.e. the very latest): the issue is fixed here

Are you talking about the two different issues of the 500 errors and
> the conf per vhost, or am i misunderstanding you? :)
>

I'm talking about the vhost conf issue.

As far as the 500 errors: I didn't know the connection between 500 errors
and the conf issue in your initial e-mail. But they could be related since
some 500 errors have to be addressed with config changes (maybe increasing a
timeout), and config changes may get confusing due to the vhost conf issue.

>
> > Previously, server config settings had an interesting property. If you
> only
> > set them at global scope, they applied to virtual hosts too. But once
> you
> > configured one mod_fcgid directive in the vhost the other fcgid settings
> > would revert to their defaults for that virtual host. (The same was true
> > for per-directory settings.)
> So if I fix that in my config, I should be fine?
>
>
I think the conf settings work with mod_fcgid 2.2 if you replicate all
server config/virtual host settings into every vhost, perhaps using the
include file mechanism in the blog you pointed to.

mod_fcgid 2.2 would let you set a number of directives inside a vhost even
though they were ignored. But I guess if you define everything at global
scope as well as in every vhost you work around that.

walterheck at gmail

Oct 6, 2009, 9:44 AM

Post #5 of 7 (279 views)
Permalink

Re: mod_fcgid: settings needed in every vhost? [In reply to]

Hi Jeff,

On Mon, Oct 5, 2009 at 07:00, Jeff Trawick <trawick[at]gmail.com> wrote:
> I think the conf settings work with mod_fcgid 2.2 if you replicate all
> server config/virtual host settings into every vhost, perhaps using the
> include file mechanism in the blog you pointed to.
>
FYI: I went through worlds of pain (we're using ispcp
(http://isp-control.net/) which does 'interesting' things to your
apache conf) but I managed to get an Include with the mod_fcgid
settings i needed into every vhost. The 500 errors are now in the
past. I don't feel too comfortable running svn-builds on a production
box :)

thanks for the help/confirmation/explanation!

Walter

paul at city-fan

Oct 15, 2009, 5:00 AM

Post #6 of 7 (223 views)
Permalink

Re: mod_fcgid: settings needed in every vhost? [In reply to]

On Mon, 5 Oct 2009 06:31:31 +0700
Walter Heck <walterheck[at]gmail.com> wrote:
> > (If you want help here you need to use the ASF-distributed
> > mod_fcgid, not the now-ancient mod_fcgid 2.2.)
> Not a big fan of self-compiled stuff on production systems. I presume
> there is no RHEL5 rpm yet? Is anybody on this list sitting on one by
> any chance?

Packages for EL-4, EL-5 and all Fedoras from FC-2 available here:

http://mirror.city-fan.org/ftp/contrib/websrv/

Cheers, Paul.

walterheck at gmail

Oct 15, 2009, 6:37 AM

Post #7 of 7 (219 views)
Permalink

Re: mod_fcgid: settings needed in every vhost? [In reply to]

That is great! Thanks Paul!

On Thu, Oct 15, 2009 at 19:00, Paul Howarth <paul[at]city-fan.org> wrote:
> On Mon, 5 Oct 2009 06:31:31 +0700
> Walter Heck <walterheck[at]gmail.com> wrote:
>> > (If you want help here you need to use the ASF-distributed
>> > mod_fcgid, not the now-ancient mod_fcgid 2.2.)
>> Not a big fan of self-compiled stuff on production systems. I presume
>> there is no RHEL5 rpm yet? Is anybody on this list sitting on one by
>> any chance?
>
> Packages for EL-4, EL-5 and all Fedoras from FC-2 available here:
>
> http://mirror.city-fan.org/ftp/contrib/websrv/
>
> Cheers, Paul.
>

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com