Re: Bug: apache/mod_svn intermittently creates transaction dirs with incorrect permissions or ownership such that the transaction breaks.
John Duprey <[email protected]> Fri, 16 Sep 2005 16:23:17 -0400
| Newsgroups | gmane.comp.version-control.subversion.devel,gmane.mail.eyebrowse.user |
|---|---|
| Message-ID | <80f71dfb050916132312a77c28__2835.67265510118$1126902484$gmane$org@mail.gmail.com> |
> > In my apache configuration (which is 1.3, but I imagine 2.x on UNIX is > similar), there's a single parent process run as root, and a number of > children running as 'nobody'. The children handle requests, while the > parent binds to port 80 and manages the children. I have verified that the children are running as user apache, the parent as root.. but I have not run something to check continuously: <PRE> root 11106 0.0 0.1 14420 6428 ? S 16:02 0:00 /usr/local/bin/httpd -k start apache 11107 0.0 0.1 14828 7188 ? S 16:02 0:00 \_ /usr/local/bin/httpd -k start apache 11108 0.0 0.1 14556 6564 ? S 16:02 0:00 \_ /usr/local/bin/httpd -k start apache 11109 0.0 0.2 16372 8500 ? S 16:02 0:00 \_ /usr/local/bin/httpd -k start apache 11110 0.0 0.1 14420 6492 ? S 16:02 0:00 \_ /usr/local/bin/httpd -k start apache 11111 0.0 0.1 14420 6492 ? S 16:02 0:00 \_ /usr/local/bin/httpd -k start apache 11113 0.0 0.1 14420 6496 ? S 16:02 0:00 \_ /usr/local/bin/httpd -k start </PRE> Could you add something to your monitoring script to capture the whole > process tree every couple of seconds? It's always possible, I suppose, > that one of the apache children is erroneously running as root. I can try it. You said you were originally running RHEL3. I assume that this means we > can discount any SELinux interaction? After scouring the server myself, I asked a dedicated admin to look too. I don't think there's external processes or security configurations that are messing with this. It seems like either apache or mod_svn breaking each other. Is it ever possible that the parent process (that is running as root) would handle some part of the request?? ...Or perhaps apache is mis-configured, although I've whittled the config down to a bare minimum and still got this error. Regards, > Malcolm >