I am running a Suse 10.1 Linux machine with apache 2, subversion and hopefully svnmanager in a few days.
My problem is that if I try to create a new repository with svnmanager I get the message that the repository was created, but if I look at the folder it is empty. So it seems svnadmin was not executed properly.
To make a test, I copied in that folder I svnmanager just created an old repository to check other functions of svnmanager. I tried to change the user privileges. As an output I get this message:
svn: Can't check path '/root/.subversion': Permission denied (cmd: /usr/bin/svn list --non-interactive file:///srv/svn/managedrepos/meins)
Command used: /usr/bin/svn list --non-interactive file:///srv/svn/managedrepos/meins
When I execute /usr/bin/svn list --non-interactive file:///srv/svn/managedrepos/meins on my shell I get the correct results.
I gave full rights to the repository in case the svn command is executet by what ever a user...
Because apache runs as user wwwrun I tried as root sudo -u wwwrun /usr/bin/svn list --non-interactive file:///srv/svn/managedrepos/meins and got the correct results.
After reading my posting a second time I saw that "Can't check path '/root/.subversion':" and I think svn is called as user root, because /root.subversion is the place where subversion stores client information... Why does it gets startet as root if my apache is running as wwwrun? And if svn tries to access this folder as user wwwrun it is clear why it is not allowed to do any file operations.
If I do a chmod 777 with the /root/.subversion the svn command seems to work but creating a new repository still results in an empty folder so that I think svnadmin is not executed properly
It seems that there is something wrong with permissions but I have no clue where to look...
Does anybody have a hint for me?
Andreas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After loking at this http://sourceforge.net/forum/forum.php?thread_id=1363337&forum_id=459311 thread I had a look at the home directory of the user wwwrun. It is set to /var/lib/wwwrun and there is a directory .subversion for user dependend subversion settings. The strange thing is that most of the folders are empty where usaly data is stored about previous repository acess.
Does anybody know why the svn commands seem to be called as user root? Or it least it looks like that because it tries to access the roots user data.
Is this a Suse specific problem or does anybody sucessfully installed svnmanager on a suse machine`?
Andreas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have one apache process running as root. Does that mean anything for svnmanager and my specific problem? The apache installation is the standart one that comes with suse without any changes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please change the home directory of the wwwrun user to e.g. /home/wwwrun and create this folder with the appropriate ownership an permissions. Currently, the homedir is probably set to /root/..
With Suse, you can change the password file with the vipw command.
Kind regards,
Marijn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here is what was written in my pw file:
wwwrun❌30:8:WWW daemon apache:/var/lib/wwwrun:/bin/false
I changed it to:
wwwrun❌30:8::/home/wwwrun:/bin/false
and it worked. Can someone tell my what is the difference between both? Did I open up a possible security problem with apache or the wwwrun user when changing the passwd file?
Thanks for any hints
Andreas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am running a Suse 10.1 Linux machine with apache 2, subversion and hopefully svnmanager in a few days.
My problem is that if I try to create a new repository with svnmanager I get the message that the repository was created, but if I look at the folder it is empty. So it seems svnadmin was not executed properly.
To make a test, I copied in that folder I svnmanager just created an old repository to check other functions of svnmanager. I tried to change the user privileges. As an output I get this message:
svn: Can't check path '/root/.subversion': Permission denied (cmd: /usr/bin/svn list --non-interactive file:///srv/svn/managedrepos/meins)
Command used: /usr/bin/svn list --non-interactive file:///srv/svn/managedrepos/meins
When I execute /usr/bin/svn list --non-interactive file:///srv/svn/managedrepos/meins on my shell I get the correct results.
I gave full rights to the repository in case the svn command is executet by what ever a user...
Because apache runs as user wwwrun I tried as root sudo -u wwwrun /usr/bin/svn list --non-interactive file:///srv/svn/managedrepos/meins and got the correct results.
After reading my posting a second time I saw that "Can't check path '/root/.subversion':" and I think svn is called as user root, because /root.subversion is the place where subversion stores client information... Why does it gets startet as root if my apache is running as wwwrun? And if svn tries to access this folder as user wwwrun it is clear why it is not allowed to do any file operations.
If I do a chmod 777 with the /root/.subversion the svn command seems to work but creating a new repository still results in an empty folder so that I think svnadmin is not executed properly
It seems that there is something wrong with permissions but I have no clue where to look...
Does anybody have a hint for me?
Andreas
After loking at this http://sourceforge.net/forum/forum.php?thread_id=1363337&forum_id=459311 thread I had a look at the home directory of the user wwwrun. It is set to /var/lib/wwwrun and there is a directory .subversion for user dependend subversion settings. The strange thing is that most of the folders are empty where usaly data is stored about previous repository acess.
Does anybody know why the svn commands seem to be called as user root? Or it least it looks like that because it tries to access the roots user data.
Is this a Suse specific problem or does anybody sucessfully installed svnmanager on a suse machine`?
Andreas
I have done a ps -ef |grep httpd to see which users are running my apache server
here is the result:
root 8951 1 0 14:33 ? 00:00:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 8952 8951 0 14:33 ? 00:00:06 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 8953 8951 0 14:33 ? 00:00:09 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 8954 8951 0 14:33 ? 00:00:06 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 8955 8951 0 14:33 ? 00:00:06 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 8956 8951 0 14:33 ? 00:00:10 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 8960 8951 0 14:33 ? 00:00:07 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 9420 8951 0 15:08 ? 00:00:02 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 9585 8951 0 15:17 ? 00:00:01 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 9609 8951 0 15:19 ? 00:00:01 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
I have one apache process running as root. Does that mean anything for svnmanager and my specific problem? The apache installation is the standart one that comes with suse without any changes.
Hi Andreas,
Please change the home directory of the wwwrun user to e.g. /home/wwwrun and create this folder with the appropriate ownership an permissions. Currently, the homedir is probably set to /root/..
With Suse, you can change the password file with the vipw command.
Kind regards,
Marijn
Thank you for the hint.
Here is what was written in my pw file:
wwwrun❌30:8:WWW daemon apache:/var/lib/wwwrun:/bin/false
I changed it to:
wwwrun❌30:8::/home/wwwrun:/bin/false
and it worked. Can someone tell my what is the difference between both? Did I open up a possible security problem with apache or the wwwrun user when changing the passwd file?
Thanks for any hints
Andreas