prefork

On Jun 21, 3:42 pm, Joe <[EMAIL PROTECTED]> wrote:
> Are you using Apache Prefork or MPM?
>
> On Jun 21, 9:39 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> wrote:
>
> > Error can be seen herehttp://beta.atlantaicecompany.com/
>
> > AGDWeb is an app in a totally separate project under the same
> > PythonPath.  It has a separate settings file.
>
> > I am not using any Django cache, I am referring to some sort of
> > internal caching that mod_python is doing.
>
> > The settings file looks like this
>
> > <VirtualHost *>
> >         ServerName beta.atlantaicecompany.com
> >         ServerAdmin [EMAIL PROTECTED]
> >         DocumentRoot /djangosites/atlantaice/
> >         <Location "/">
> >                 SetHandler python-program
> >                 PythonHandler django.core.handlers.modpython
> >                 SetEnv DJANGO_SETTINGS_MODULE atlantaice.settings
> >                 PythonPath "['/djangosites/'] + sys.path"
> >                 PythonDebug Off
> >         </Location>
> >         <Location "/images">
> >                 SetHandler None
> >         </Location>
> >         <Location "/js">
> >                 SetHandler None
> >         </Location>
> >         <Location "/flash">
> >                 SetHandler None
> >         </Location>
> >         <Location "/admin-media">
> >                 SetHandler None
> >         </Location>
>
> >         ErrorLog /var/log/apache2/beta.atlantaicecompany.com-error.log
>
> >         # Possible values include: debug, info, notice, warn, error,
> > crit,
> >         # alert, emerg.
> >         LogLevel warn
>
> >         CustomLog /var/log/apache2/beta.atlantaicecompany.com-
> > access.log combined
> >         ServerSignature Off
> > </VirtualHost>
>
> > and
>
> > <VirtualHost *>
> >         ServerName agdweb.gtagd.org
> >         ServerAdmin [EMAIL PROTECTED]
> >         DocumentRoot /djangosites/AGD/
> >         <Location "/">
> >                 SetHandler python-program
> >                 PythonHandler django.core.handlers.modpython
> >                 SetEnv DJANGO_SETTINGS_MODULE AGD.settings
> >                 PythonPath "['/djangosites/'] + sys.path"
> >                 PythonDebug Off
> >         </Location>
> >         <Location "/site-media">
> >                 SetHandler None
> >         </Location>
> >         <Location "/admin-media">
> >                 SetHandler None
> >         </Location>
>
> >         ErrorLog /var/log/apache2/agdweb.gtagd.org-error.log
>
> >         # Possible values include: debug, info, notice, warn, error,
> > crit,
> >         # alert, emerg.
> >         LogLevel warn
>
> >         CustomLog /var/log/apache2/agdweb.gtagd.org-access.log
> > combined
> >         ServerSignature Off
> > </VirtualHost>
>
> > On Jun 21, 5:45 am, Graham Dumpleton <[EMAIL PROTECTED]>
> > wrote:
>
> > > On Jun 21, 5:46 pm, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote
>
> > > > On 21-Jun-07, at 12:50 PM, [EMAIL PROTECTED] wrote:
>
> > > > > cache gets confused.  But if I do that, the settings don't work
> > > > > correctly and the site won't load.  What am I doing wrong?
>
> > > > you need a pythonInterpretor line in each Location with a different
> > > > name. It is in the documentation
>
> > > Not true if each is in its own VirtualHost as the default behaviour of
> > > mod_python is to give each VirtualHost its own sub interpreter. You
> > > should only need to set PythonInterpreter if you were running two
> > > Django instances within the same VirtualHost at different mount
> > > points.
>
> > > For completeness, it would help if OP posted both VirtualHost
> > > configurations side by side in the same message, so one can see
> > > properly the PythonPath setting for each and the
> > > DJANGO_SETTINGS_MODULE setting.
>
> > > BTW, if using recent mod_python, to confirm that distinct Python sub
> > > interpreters are being used one can use:
>
> > >   from mod_python import apache
> > >   apache.log_error("INTERPRETER %s" % apache.interpreter)
>
> > > Then check the Apache error log file.
>
> > > I would also suggest printing the value of sys.path to make sure it is
> > > what you expect.
>
> > > More importantly, when you say "Django's cache is confusing the two
> > > sites and is saying that one table from a project doesn't exist in the
> > > other project's db", can you post the actual full message you are
> > > getting, and state where you are getting it. If it has a traceback,
> > > also include the traceback.
>
> > > Graham


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to