Title says it all. This is a fresh Fedora 17 system running on a Xen hypervisor. No idea why it won’t start
[[email protected]~] uname -a Linux box.localhost 3.5.4-2.fc17.i686.PAE #1 SMP Wed Sep 26 22:10:23 UTC 2012 i686 i686 i386 GNU/Linux [[email protected]~] cat /etc/redhat-release Fedora release 17 (Beefy Miracle) [[email protected]~] systemctl enable httpd.service ln -s '/usr/lib/systemd/system/httpd.service' '/etc/systemd/system/multi-user.target.wants/httpd.service' [[email protected]~] systemctl start httpd.service Job failed. See system journal and 'systemctl status' for details. [[email protected]~] systemctl status httpd.service httpd.service - The Apache HTTP Server (prefork MPM) Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled) Active: failed (Result: exit-code) since Fri, 19 Oct 2012 22:43:37 -0500; 3s ago Process: 18225 ExecStart=/usr/sbin/httpd $OPTIONS -k start (code=exited, status=226/NAMESPACE) CGroup: name=systemd:/system/httpd.service Oct 19 22:43:37 box.localhost systemd: Failed at step NAMESPACE spawning /usr/sbin/httpd: No such file or directory [[email protected]~] ls -al /usr/sbin/httpd -rwxr-xr-x 1 root root 343496 Apr 30 04:56 /usr/sbin/httpd
Recent versions of Fedora/systemd include a new feature which generates random private directories in
/var/tmp for individual system services.
This means that there are things you should check:
- DO NOT symlink
/tmpor vice versa. These are treated separately and so you’ll need to keep them separate.
- Ensure that both
/tmphave 1777 permissions.
If this doesn’t resolve the problem, you may have found a bug, and should report it.
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.