Anyone know why these services aren't starting up? It would be awesome if the error messages would actually give some detail...
This all started when I upgraded to Fedora 15. Am hoping *not* to reinstall.
Code:
[root@server system]# systemctl status nfs.service
nfs.service - LSB: Start up the NFS server sevice
Loaded: loaded (/etc/rc.d/init.d/nfs)
Active: failed since Tue, 31 May 2011 11:26:47 -0400; 1h 39min ago
Process: 1004 ExecStart=/etc/rc.d/init.d/nfs start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/nfs.service
[root@server system]# systemctl status nfslock.service
nfslock.service - LSB: Start up the NFS file locking sevice
Loaded: loaded (/etc/rc.d/init.d/nfslock)
Active: failed since Tue, 31 May 2011 11:26:47 -0400; 1h 39min ago
Process: 1005 ExecStart=/etc/rc.d/init.d/nfslock start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/nfslock.service
[root@server system]# systemctl status systemd-kmsg-syslogd.service
systemd-kmsg-syslogd.service - Syslog Kernel Log Buffer Bridge
Loaded: loaded (/lib/systemd/system/systemd-kmsg-syslogd.service)
Active: failed since Tue, 31 May 2011 11:26:29 -0400; 1h 39min ago
Process: 404 ExecStart=/lib/systemd/systemd-kmsg-syslogd (code=exited, status=218/CAPABILITIES)
CGroup: name=systemd:/system/systemd-kmsg-syslogd.service
[root@server system]# systemctl status systemd-logger.service
systemd-logger.service - Stdio Syslog Bridge
Loaded: loaded (/lib/systemd/system/systemd-logger.service)
Active: failed since Tue, 31 May 2011 11:26:30 -0400; 1h 39min ago
Process: 422 ExecStart=/lib/systemd/systemd-logger (code=exited, status=218/CAPABILITIES)
CGroup: name=systemd:/system/systemd-logger.service
Here are some more details from /var/log/messages:
Code:
May 30 22:04:12 server kernel: <30>systemd[1]: systemd 26 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; fedora)
May 30 22:04:12 server kernel: <28>systemd[1]: /sbin/modprobe failed with error code 1.
May 30 22:04:12 server kernel: <30>systemd[1]: Set hostname to <servername>.
May 30 22:04:12 server kernel: <28>systemd[1]: /usr appears to be on a different file system than /. This is not supported anymore. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more information.
May 30 22:04:12 server kernel: <28>systemd[1]: No control group support available, not creating root group.
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory
May 30 22:04:12 server kernel: <29>systemd[1]: Unit proc-sys-fs-binfmt_misc.automount entered failed state.
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory
May 30 22:04:12 server kernel: <29>systemd[1]: Unit dev-hugepages.automount entered failed state.
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory
May 30 22:04:12 server kernel: <29>systemd[1]: Unit sys-kernel-debug.automount entered failed state.
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory
May 30 22:04:12 server kernel: <29>systemd[1]: Unit sys-kernel-security.automount entered failed state.
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory
May 30 22:04:12 server kernel: <29>systemd[1]: Unit dev-mqueue.automount entered failed state.
May 30 22:04:12 server kernel: <29>systemd[1]: systemd-kmsg-syslogd.service: main process exited, code=exited, status=218
May 30 22:04:12 server kernel: <29>systemd[1]: Unit systemd-kmsg-syslogd.service entered failed state.
May 30 22:04:12 server kernel: <29>systemd[1]: systemd-logger.service: main process exited, code=exited, status=218
May 30 22:04:12 server kernel: <29>systemd[1]: Unit systemd-logger.service entered failed state.
May 30 22:04:12 server kernel: <29>systemd[1]: systemd-logger.service: main process exited, code=exited, status=218
May 30 22:04:12 server kernel: <29>systemd[1]: Unit systemd-logger.service entered failed state.
May 30 22:04:12 server kernel: <29>systemd[1]: systemd-logger.service: main process exited, code=exited, status=218
May 30 22:04:12 server kernel: <29>systemd[1]: Unit systemd-logger.service entered failed state.
May 30 22:04:12 server kernel: <29>systemd[1]: systemd-logger.service: main process exited, code=exited, status=218
May 30 22:04:12 server kernel: <29>systemd[1]: Unit systemd-logger.service entered failed state.
May 30 22:04:12 server kernel: <29>systemd[1]: systemd-logger.service: main process exited, code=exited, status=218
May 30 22:04:12 server kernel: <29>systemd[1]: Unit systemd-logger.service entered failed state.
May 30 22:04:12 server kernel: <29>systemd[1]: systemd-logger.service: main process exited, code=exited, status=218
May 30 22:04:12 server kernel: <29>systemd[1]: Unit systemd-logger.service entered failed state.
May 30 22:04:12 server kernel: <28>systemd[1]: systemd-logger.service start request repeated too quickly, refusing to start.
Code:
May 30 22:04:19 server systemd[1]: nfslock.service: control process exited, code=exited status=1
May 30 22:04:19 server systemd[1]: Unit nfslock.service entered failed state.
Code:
May 30 23:35:51 server systemd[1]: nfs.service: control process exited, code=exited status=1
May 30 23:35:52 server systemd[1]: Unit nfs.service entered failed state.
For a manual restart of nfs, here's the error:
Code:
May 31 13:19:25 server kernel: [ 6782.902700] svc: failed to register lockdv1 RPC service (errno 111).
May 31 13:19:25 server kernel: [ 6782.923573] svc: failed to register lockdv1 RPC service (errno 111).
May 31 13:19:25 server systemd[1]: nfs.service: control process exited, code=exited status=1
May 31 13:19:25 server systemd[1]: Unit nfs.service entered failed state.
And here's what it shows on the command line:
Code:
# /etc/rc.d/init.d/nfs start
Starting nfs (via systemctl): Error: No space left on device
Job failed. See system logs and 'systemctl status' for details.
[FAILED]
uh, what?! I'm definitely NOT out of space on the device.