That was exactly the problem. I installed mod_wsgi 2.4 and now things
work great.

On Apr 14, 2:08 pm, Graham Dumpleton <[email protected]>
wrote:
> Upgrade to mod_wsgi 2.4 or turn KeepAlive off in Apache. See:
>
>  http://code.google.com/p/modwsgi/issues/detail?id=132&can=1&start=100
>
> At least it sounds like that problem.
>
> The advice in:
>
>  http://trac.edgewall.org/wiki/TracModWSGI
>
> about version to use should really be changed from 2.3 to 2.4.
>
> I'll try and do this later if get a chance and if no one else has got
> there before me.
>
> Graham
>
> On Apr 15, 3:06 am, Kamil Kisiel <[email protected]> wrote:
>
> > I'm trying to run Trac 0.11.4 on Apache 2.2.10 withmod_wsgi2.3 on
> > openSUSE 11.1
>
> > The site itself works fine, however hardly any of the stylesheets or
> > images from /chrome/ are served to the browser. The only ones that
> > seem to make it are /chrome/common/trac.css and /chrome/common/
> > dots.gif
>
> > For the remainder of the /chrome/ content the browser gets the headers
> > correctly, but the response is blank. I tested this with Firebug.
>
> > Using debug logging in trac, there are no obvious failures. Every
> > request returns a message like:
>
> > 2009-04-14 10:00:36,792 Trac[main] DEBUG: Dispatching <Request "GET u'/
> > chrome/common/topbar_gradient.png'">
> > 2009-04-14 10:00:36,805 Trac[main] DEBUG: Dispatching <Request "GET u'/
> > chrome/common/topbar_gradient2.png'">
>
> > In the apache logs, every request has HTTP code 200, so all looks good
> > from that end as well.
>
> > As a test, I ran the same site under tracd and everything works
> > perfectly with that setup, so there is obviously something wrong when
> > running under wsgi.
>
> > Here's a copy of my virtual host configuration which I took from our
> > current trac server which is running on Gentoo under fcgi, and
> > modified it for use on the new openSUSE server with wsgi. Domain names
> > have been anonymized to protect the innocent ;)
>
> > <VirtualHost *:80>
> >   ServerName trac2.lan.foo.com
> >   ServerAlias trac2 trac2.lan
>
> >   # Logging
> >   LogLevel warn
> >   ErrorLog /var/log/apache2/trac.lan.foo.com-error_log
> >   CustomLog /var/log/apache2/trac.lan.foo.com-access_log combined
>
> >   # Rewrite all other domains to trac.lan.foo.com
> >   RewriteEngine on
> >   RewriteCond %{HTTP_HOST} !^trac2\.lan\.zfoo\.com
> >   RewriteRule ^(.*)http://trac2.lan.foo.com$1[L,R=301]
>
> >   DocumentRoot "/srv/www/vhosts/trac.lan.foo.com/htdocs/"
> >   ErrorDocument 500 "Don't panic. Have a beer. Call your parents. The
> > server has encountered a temporary error. Wait a minute, reload the
> > page, and everything should be fine. If not, then tell someone."
>
> >   WSGIScriptAlias / /srv/www/vhosts/trac.lan.foo.com/cgi-bin/trac.wsgi
> >   <Directory /srv/www/vhosts/trac.lan.foo.com/cgi-bin/>
> >     #WSGIApplicationGroup %{GLOBAL}
> >     AllowOverride None
> >     Order allow,deny
> >     Allow from all
> >   </Directory>
>
> >   # Require LDAP authentication
> >   <Location "/login">
> >     AuthType basic
> >     AuthName "foo"
> >     AuthBasicProvider ldap
> >     AuthLDAPURL ldap://ldapurl
> >     AuthzLDAPAuthoritative on
> >     AuthLDAPGroupAttribute memberUid
> >     AuthLDAPGroupAttributeIsDN off
> >     Require valid-user
> >   </Location>
> > </VirtualHost>
>
> > I'm pretty much at a loss now as to how to further debug this problem.
> > None of the logs seem to indicate any issues and everything runs well
> > under tracd. Any insight would be much appreciated.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to