Apache2 chroot /dev/null permission denied
in [Debian]
|
From: Knowledge Seeker on 17 Mar 2010 18:50 Hi, I have an old Debian Etch box, running Apache2 on chroot jail. Yesterday, (it sounds like joke) I turned off the machine and when I started it again the web server did not come to life again. The problem was a Permission Denied on the /dev/null. I created my device with the command: mknod -m 0666 /chroot/dev/null c 1 3 listing the permissions: crw-rw-rw- 1 root root 1, 3 2010-03-16 18:37 null crw-rw-rw- 1 root root 1, 8 2010-03-16 18:39 random crw-rw-rw- 1 root root 1, 9 2010-03-16 18:39 urandom (When I change the group to sys, don't solve the problem) Even outside of the chroot when I try to echo something and redirect to this device I get the same message: -su: null: Permission Denied My kernel is the default: 2.6.18-6-686 #1 SMP Everything worked fine 2 days ago. I really wish to understand and solve this issue. When I mount all /dev with a bind option, it works fine again, but I wouldn't want to have all my devices available inside chroot. I really appreciate any help. Thanks in advance -- Knoseeker
From: Wayne on 17 Mar 2010 19:30 Knowledge Seeker wrote: > Hi, > I have an old Debian Etch box, running Apache2 on chroot jail. Yesterday, > (it sounds like joke) I turned off the machine and when I started it again > the web server did not come to life again. > The problem was a Permission Denied on the /dev/null. > > I created my device with the command: mknod -m 0666 /chroot/dev/null c 1 3 > listing the permissions: > > crw-rw-rw- 1 root root 1, 3 2010-03-16 18:37 null > crw-rw-rw- 1 root root 1, 8 2010-03-16 18:39 random > crw-rw-rw- 1 root root 1, 9 2010-03-16 18:39 urandom > > > (When I change the group to sys, don't solve the problem) > > Even outside of the chroot when I try to echo something and redirect to this > device I get the same message: > > -su: null: Permission Denied > > My kernel is the default: > 2.6.18-6-686 #1 SMP > > Everything worked fine 2 days ago. > > I really wish to understand and solve this issue. > When I mount all /dev with a bind option, it works fine again, but I I ran into that after an upgrade on squeeze a few months ago. As a result a few programs would not run. The atd daemon was the only one I cared about. Don't know, yet, what caused it but the fix was to put the following into /root/.bash_profile. chmod 666 /dev/null chgrp root /dev/null /etc/init.d/atd restart HTH Wayne -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4BA16444.4010909(a)gmail.com
From: Knowledge Seeker on 17 Mar 2010 22:10 That is the problem. The permission is set to 666 and the group is root. But it still don't work. On Wed, Mar 17, 2010 at 11:22 PM, Wayne <linuxtwo(a)gmail.com> wrote: > Knowledge Seeker wrote: > >> Hi, >> I have an old Debian Etch box, running Apache2 on chroot jail. Yesterday, >> (it sounds like joke) I turned off the machine and when I started it again >> the web server did not come to life again. >> The problem was a Permission Denied on the /dev/null. >> >> I created my device with the command: mknod -m 0666 /chroot/dev/null c 1 >> 3 >> listing the permissions: >> >> crw-rw-rw- 1 root root 1, 3 2010-03-16 18:37 null >> crw-rw-rw- 1 root root 1, 8 2010-03-16 18:39 random >> crw-rw-rw- 1 root root 1, 9 2010-03-16 18:39 urandom >> >> >> (When I change the group to sys, don't solve the problem) >> >> Even outside of the chroot when I try to echo something and redirect to >> this >> device I get the same message: >> >> -su: null: Permission Denied >> >> My kernel is the default: >> 2.6.18-6-686 #1 SMP >> >> Everything worked fine 2 days ago. >> >> I really wish to understand and solve this issue. >> When I mount all /dev with a bind option, it works fine again, but I >> > > I ran into that after an upgrade on squeeze a few months ago. As a result > a few programs would not run. The atd daemon was the only one I cared > about. Don't know, yet, what caused it but the fix was to put the following > into /root/.bash_profile. > > chmod 666 /dev/null > chgrp root /dev/null > > /etc/init.d/atd restart > > HTH > > Wayne > > > -- > To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a > subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org > Archive: http://lists.debian.org/4BA16444.4010909(a)gmail.com > > -- Knoseeker
From: Wayne on 18 Mar 2010 11:20 Knowledge Seeker wrote: > That is the problem. > The permission is set to 666 and the group is root. > But it still don't work. > > I don't know know what else to suggest. Maybe it is time to upgrade to lenny? Sorry I could not be of more help. Wayne -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4BA2429E.9060504(a)gmail.com
From: Mike Bird on 18 Mar 2010 16:00
On Wed March 17 2010 19:00:35 Knowledge Seeker wrote: > That is the problem. > The permission is set to 666 and the group is root. > But it still don't work. Please post the exact complete error message, and also the results of the following three commands run as root as soon as possible after the error occurs: # ls -dl /dev drwxr-xr-x 22 root root 6280 2010-03-14 11:16 /dev # ls -l /dev/null crw-rw-rw- 1 root root 1, 3 2010-03-14 11:15 /dev/null # su www-data -c 'ls -l /dev/null' crw-rw-rw- 1 root root 1, 3 2010-03-14 11:15 /dev/null Is there anything in your Apache config that might be trying to chroot? --Mike Bird -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/201003181252.37677.mgb-debian(a)yosemite.net |