On Thu, May 26, 2011 at 12:01 PM, Kevin Falcone <falc...@bestpractical.com> wrote: > On Thu, May 26, 2011 at 11:37:24AM -0400, Asif Iqbal wrote: >> root@lucid:/opt/rt4/var/mason_data# ls -al >> total 4 >> drwxrwx--- 4 www-data www-data 1024 2011-05-25 17:21 . >> drwxr-xr-x 5 root root 1024 2011-05-20 12:42 .. >> drwxr-xr-x 2 root root 1024 2011-05-25 17:21 cache >> drwxr-xr-x 2 root root 1024 2011-05-25 17:21 obj >> I need help to find out why mason_data/{cache,obj} are owned by root. >> I removed the dirs and restarted apache2 and they come back with root >> as the owner > > Check your apache config. Mostly likely you're loading the RT configs > before the User/Group lines which means the initial setup gets done as > root instead the web user.
root@lucid:/etc/apache2# cat /etc/apache2/envvars ... export APACHE_RUN_USER=www-data export APACHE_RUN_GROUP=www-data ... root@lucid:/etc/apache2# egrep -n "^User|^Group" apache2.conf 145:User ${APACHE_RUN_USER} 146:Group ${APACHE_RUN_GROUP} root@lucid:/etc/apache2# grep -n ^Include apache2.conf 204:Include /etc/apache2/mods-enabled/*.load 205:Include /etc/apache2/mods-enabled/*.conf 208:Include /etc/apache2/httpd.conf 211:Include /etc/apache2/ports.conf 233:Include /etc/apache2/conf.d/ 236:Include /etc/apache2/sites-enabled/ User is defined on line 145 and on line 236 /etc/apache2/sites-enabled/ dir is included. Here is the conf for webrt. So it is included after User and Group are defined root@lucid:/etc/apache2# cat /etc/apache2/sites-enabled/webrt <VirtualHost *:80> ### Optional apache logs for RT ErrorLog /var/log/apache2/rt.error TransferLog /var/log/apache2/rt.access LogLevel debug AddDefaultCharset UTF-8 DocumentRoot "/opt/rt4/share/html" <Location /> Order allow,deny Allow from all SetHandler perl-script PerlResponseHandler Plack::Handler::Apache2 PerlSetVar psgi_app /opt/rt4/sbin/rt-server </Location> <Perl> use Plack::Handler::Apache2; Plack::Handler::Apache2->preload("/opt/rt4/sbin/rt-server"); </Perl> </VirtualHost> > > -kevin > >> root@lucid:/opt/rt4/var/mason_data# /etc/init.d/apache2 stop >> * Stopping web server apache2 >> ... waiting ........... >> >> [ OK ] >> root@lucid:/opt/rt4/var/mason_data# ls -al >> total 4 >> drwxrwx--- 4 www-data www-data 1024 2011-05-25 17:21 . >> drwxr-xr-x 5 root root 1024 2011-05-20 12:42 .. >> drwxr-xr-x 2 root root 1024 2011-05-25 17:21 cache >> drwxr-xr-x 2 root root 1024 2011-05-25 17:21 obj >> root@lucid:/opt/rt4/var/mason_data# rm -rf cache obj >> root@lucid:/opt/rt4/var/mason_data# ls -al >> total 2 >> drwxrwx--- 2 www-data www-data 1024 2011-05-26 11:34 . >> drwxr-xr-x 5 root root 1024 2011-05-20 12:42 .. >> root@lucid:/opt/rt4/var/mason_data# /etc/init.d/apache2 start >> * Starting web server apache2 >> [ OK ] >> root@lucid:/opt/rt4/var/mason_data# ls -al >> total 4 >> drwxrwx--- 4 www-data www-data 1024 2011-05-26 11:34 . >> drwxr-xr-x 5 root root 1024 2011-05-20 12:42 .. >> drwxr-xr-x 2 root root 1024 2011-05-26 11:34 cache >> drwxr-xr-x 2 root root 1024 2011-05-26 11:34 obj >> root@lucid:/opt/rt4/var/mason_data# ps -ef | grep apache2 >> root 2192 1 27 11:34 ? 00:00:04 /usr/sbin/apache2 -k start >> www-data 2195 2192 0 11:34 ? 00:00:00 /usr/sbin/apache2 -k start >> root 2198 1367 0 11:34 pts/0 00:00:00 grep --color=auto apache2 >> root@lucid:/opt/rt4/var/mason_data# ps -ef | grep apache2 >> root 2192 1 20 11:34 ? 00:00:05 /usr/sbin/apache2 -k start >> www-data 2195 2192 0 11:34 ? 00:00:00 /usr/sbin/apache2 -k start >> www-data 2199 2192 2 11:34 ? 00:00:00 /usr/sbin/apache2 -k start >> www-data 2200 2192 2 11:34 ? 00:00:00 /usr/sbin/apache2 -k start >> root 2256 1367 0 11:34 pts/0 00:00:00 grep --color=auto apache2 >> root@lucid:/opt/rt4/var/mason_data# >> >> >> -- >> Asif Iqbal >> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu >> A: Because it messes up the order in which people normally read text. >> Q: Why is top-posting such a bad thing? > -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?