[rt-users] mason_data dir contents owned by root

[Kevin Falcone]

On Thu, May 26, 2011 at 11:37:24AM -0400, Asif Iqbal wrote:
> root at 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.

-kevin

> root at lucid:/opt/rt4/var/mason_data# /etc/init.d/apache2 stop
>  * Stopping web server apache2
>                                           ... waiting ...........
> 
>     [ OK ]
> root at 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 at lucid:/opt/rt4/var/mason_data# rm -rf cache obj
> root at 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 at lucid:/opt/rt4/var/mason_data# /etc/init.d/apache2 start
>  * Starting web server apache2
>                                   [ OK ]
> root at 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 at 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 at 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 at 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?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20110526/962e7671/attachment.sig>