Re: [cpx] cpx and apache, didnt work

["Jonathan Linowes" <jonathan@xxxxxxxxxxx>]

hi Steve,
thanks again for your suggestion.
However, I made the change (B) to one one of my domains (Added the CPX stuff 
inside the virtual host stuff) and it still broke my other virtual domains. 
Here's a possible explanation of what might be going on from another list 
(though I don't fully understand what he's saying). I welcome other 
suggestions for things to try (other than the "separate apache daemons" 
which kind of scares me :)




> I've seen this problem before on sites here at work.
> Perl seems to be especially good at polluting the apache environment. I
> even had one perl site screwing up all the apache environment variables
> for the 50 other php virtual hosts running on the same server.
>
> In the end it seemed to be the way the perl was written (badly) and the
> use of mod_perl.
>
> Removing mod_perl helped as did rewriting some of the perl scripts to
> not use the apache variable names.
>
> I still think it is a mod_perl bug since it shouldn't be possible for a
> perl script running on one virtual host to affect sites running on other
> virtual hosts just because they're part of the same Apache daemon.
>
> Suffice to say it is the perl environment's fault and not Xaraya or
> PHP's. An easy way to test it to load phpinfo up for the problem php
> site and keep refreshing while someone browses the perl bit - you will
> see all the apache environment variables are totally screwed - including
> rather notably PATH_INFO which is what short urls need. Hence it is
> trying to load allfunctions.js as a module.
>
> Turning off short urls seems to get rid of the problem but now the
> xaraya sites are suffering for something thats not their fault and I did
> find that some other operations were slightly temperamental too as the
> environment couldnt be trusted anymore.
>
> In the end it was fixed by having totally seperate apache daemons
> running on different ports with an apache proxy on the front end farming
> the requests out to the appropriate machine:port combination for that
> virtual host. (probably not worth the effort for only a few sites - but
> this setup hosts several hundred on a mosix cluster).








----- Original Message ----- 
From: "Steve Yates" <steve@xxxxxxxxxxx>
To: <cpx@xxxxxxxxxxxxx>
Sent: Tuesday, January 18, 2005 2:30 PM
Subject: Re: [cpx] cpx and apache


> On Tue, 18 Jan 2005 13:50:03 -0500
> "Jonathan Linowes" <jonathan@xxxxxxxxxxx> wrote:
>
> > A. on domains that use the cms, add an A record so its accessed via 
> > cpx.mydomain.com
> >
> > B. on domains that don't use the cms, access control panel the normal way 
> > (mydomain.com/ControlPanel).
>
> I think you'll need to create a /ControlPanel entry in each
> vhost entry for item B.  For item A you might consider something like
> this:
>
> <VirtualHost 11.22.33.44:80>
> DocumentRoot /home/something/www/htdocs
> ServerName cpx.serverdomain.com
> ServerAlias cpx.*
> (add /ControlPanel entry here)
> </VirtualHost>
>
> The cpx.* will enable it for all domains on the server and you don't
> have to remember to add another entry later to handle future new vhosts.
>
>
> - Steve Yates
> - ITS, Inc.
> - Linux: because rebooting is for adding new hardware.
>
> ~ Taglines by Taglinator - www.srtware.com ~
>
>
> ======================================================================
> This is <cpx@xxxxxxxxxxxxx>      <http://www.groupmail.org/lists/cpx/>
> Before posting a question, please search the archives (see above URL).


======================================================================
This is <cpx@xxxxxxxxxxxxx>      <http://www.groupmail.org/lists/cpx/>
Before posting a question, please search the archives (see above URL).