In general you don't want anybody mucking around in a filesystem that is not part of the site they have sent a request to. This is the reason for not having a DocumentRoot. If the global is letting you in the put a <Directory> block in the vhost to keep them out.
The above is just good practice and has nothing to do with your issue. I didn't realize this was an intermittent issue. In that case going through the steps I outlined would be useless. If the request is not in the log access file then it would seem to me that mod_wsgi isn't even getting and apache is dropping it on the floor somewhere before sending it off to mod_wsgi. This is beginning to look like an issue concerning other modules that are being used. Graham would be the person to best answer this as soon as he comes back from his vacation/holiday. ~Carl On Wed, Oct 13, 2010 at 4:15 AM, anatoly techtonik <[email protected]> wrote: > On Wed, Oct 13, 2010 at 3:54 AM, Carl Nobile <[email protected]> wrote: >> First I wouldn't set the DocumentRoot to anything. > > Done, but how can this help? It will still be inherited from global > configuration. > >> Then I would try to see if it worked normally on port 80 by commenting >> out all the SSL stuff. Maybe temporarily use a local network address >> if you are concerned with security. > > It is not 100% repeatable, so I'd prefer to set up passive detection > to quickly jump in next time when this happens. > >> Is the path to the log file really /var/trac/log? I would think it >> should be /var/log/trac. > > Trac creates its log in its environment, so I've just gather all logs > in one place. error.log in this directory is writable by root, and I > think it is the way Apache2 writes them. > > >> >> ~Carl >> >> On Tue, Oct 12, 2010 at 6:31 PM, anatoly techtonik <[email protected]> >> wrote: >>> Daemon mode. There is also mod_php5 module on this Apache2 server. >>> >>> <VirtualHost *:443> >>> ServerName trac.example.com >>> DocumentRoot /var/trac/static/htdocs >>> ErrorLog /var/trac/log/error.log >>> LogLevel notice >>> >>> Alias /chrome /var/trac/static/htdocs >>> <Directory /var/trac/static/htdocs> >>> Order allow,deny >>> Allow from all >>> </Directory> >>> >>> >>> WSGIDaemonProcess example-trac user=trac group=trac umask=0026 >>> home=/var/trac display-name=wsgi:trac >>> WSGIProcessGroup example-trac >>> >>> WSGIScriptAlias / /var/trac/static/cgi-bin/trac.wsgi >>> >>> <Directory /var/trac/static/cgi-bin> >>> # this is needed for Subversion bindings >>> #WSGIApplicationGroup %{GLOBAL} >>> >>> Order allow,deny >>> Allow from all >>> </Directory> >>> >>> SSLEngine On >>> SSLProtocol all >>> SSLCertificateFile /etc/apache2/ssl.crt/example.com.crt >>> SSLCertificateKeyFile /etc/apache2/ssl.key/example.com.key >>> </VirtualHost> >>> >>> -- >>> anatoly t. >>> >>> >>> >>> On Tue, Oct 12, 2010 at 10:28 PM, Carl Nobile <[email protected]> wrote: >>>> Are you using daemon or embedded mode? Is PHP being used? >>>> >>>> I hope you are using daemon mode as embedded mode will have tons of >>>> issues with other mods on the system PHP being one. >>>> >>>> Include your apache conf for Trac please. >>>> >>>> ~Carl >>>> >>>> On Tue, Oct 12, 2010 at 3:11 PM, anatoly techtonik <[email protected]> >>>> wrote: >>>>> Only Trac is using mod_wsgi, although there are some other sites >>>>> handled by the same Apache2 instance, but I don't work with them to >>>>> know if they fail or not. >>>>> -- >>>>> anatoly t. >>>>> >>>>> >>>>> >>>>> On Tue, Oct 12, 2010 at 9:26 PM, Carl Nobile <[email protected]> >>>>> wrote: >>>>>> You say all other sites are working, but do any of these sites use >>>>>> mod_wsgi? >>>>>> >>>>>> ~Carl >>>>>> >>>>>> On Tue, Oct 12, 2010 at 11:55 AM, anatoly techtonik >>>>>> <[email protected]> wrote: >>>>>>> Hi, >>>>>>> >>>>>>> I am running Trac under mod_wsgi on Debian Lenny in daemon mode. It >>>>>>> fails quite often when editing wiki pages. Chrome shows: >>>>>>> >>>>>>> Error 101 (net::ERR_CONNECTION_RESET): Unknown error. >>>>>>> >>>>>>> All other sites work ok, so it's not a problem with my internet >>>>>>> connection. The SSH session to the same host is stable while I've >>>>>>> managed to catch about 3 connection reset errors with Trac/mod_wsgi. >>>>>>> The strange thing is that I can't see any error in Trac or Apache >>>>>>> error logs. Looks like request is just not handled. >>>>>>> >>>>>>> How can I debug the issue? >>>>>>> >>>>>>> Thanks. >>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "modwsgi" 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/modwsgi?hl=en. >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> ------------------------------------------------------------------------------- >>>>>> Carl J. Nobile (Software Engineer) >>>>>> [email protected] >>>>>> ------------------------------------------------------------------------------- >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "modwsgi" 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/modwsgi?hl=en. >>>>>> >>>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google Groups >>>>> "modwsgi" 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/modwsgi?hl=en. >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> ------------------------------------------------------------------------------- >>>> Carl J. Nobile (Software Engineer) >>>> [email protected] >>>> ------------------------------------------------------------------------------- >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "modwsgi" 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/modwsgi?hl=en. >>>> >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "modwsgi" 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/modwsgi?hl=en. >>> >>> >> >> >> >> -- >> ------------------------------------------------------------------------------- >> Carl J. Nobile (Software Engineer) >> [email protected] >> ------------------------------------------------------------------------------- >> >> -- >> You received this message because you are subscribed to the Google Groups >> "modwsgi" 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/modwsgi?hl=en. >> >> > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" 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/modwsgi?hl=en. > > -- ------------------------------------------------------------------------------- Carl J. Nobile (Software Engineer) [email protected] ------------------------------------------------------------------------------- -- You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en.
