[Bug 1251939] Re: Chroot fails with Cannot chroot when not started as root error
I can confirm that Chroot is working in the proposed (2.4.6-2ubuntu2.1 ) Thank you for the fix. -Arul -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with Cannot chroot when not started as root error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1251939] Re: Chroot fails with Cannot chroot when not started as root error
Any update on when can we get a fix for this? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with Cannot chroot when not started as root error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1251939] Re: Chroot fails with Cannot chroot when not started as root error
Thank you for reviewing this bug report and assigning the severity. While I agree with you on the assigned severity of Medium, I'd like to point out that though ChrootDir is not a default option, it relates to the security of apache server. I am not sure how many users simply use the server w/ default options, but I would guess many will do server hardening starting with chrooting. Would really appreciate if this fix is included soon. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with Cannot chroot when not started as root error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1251939] [NEW] Chroot fails with Cannot chroot when not started as root error
Public bug reported: I have set my chroot directory as shown below. ChrootDir /var/www When started with the above chroot setting, apache2 exits with the following error [Sat Nov 16 13:52:40.621872 2013] [unixd:alert] [pid 3747] (34)Numerical result out of range: AH02158: Cannot chroot when not started as root NOTE: apache2 is started as 'root' user. This was reported as a bug in apache.org earlier (link below) where it was confirmed this is fixed in a trunk. https://issues.apache.org/bugzilla/show_bug.cgi?id=55787 Details of my Ubuntu server: - root@gorilla:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=13.10 DISTRIB_CODENAME=saucy DISTRIB_DESCRIPTION=Ubuntu 13.10 root@gorilla:~# apache2ctl -v Server version: Apache/2.4.6 (Ubuntu) Server built: Aug 9 2013 14:31:04 root@gorilla:~# apache2ctl -l -M Compiled in modules: core.c mod_so.c mod_watchdog.c http_core.c mod_log_config.c mod_logio.c mod_version.c mod_unixd.c mod_unixd.c ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: apache2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with Cannot chroot when not started as root error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1251939/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 937040] Re: Duplicate ufw rules installed by dovecot packages
Brian, thanks for the explanation, I had the same issue after upgrade to Precise and its all good now after removing the old/duplicate rules as per your suggestion! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/937040 Title: Duplicate ufw rules installed by dovecot packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/937040/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
