I've purged the remains of the 'portmap' package and rebooted. There
are no more mentions of 'portmap' in /var/log/syslog. statd continues
to fail in the same fashion.
I'm attaching the entire syslog since last boot, just in case. There's
something else I noticed that might be relevant: local filesystems are
mounted *after* statd fails to come up.
Sep 20 12:03:52 muskatas kernel: [ 9.614549] init: statd respawning too
fast, stopped
Sep 20 12:03:52 muskatas kernel: [ 10.204317] EXT4-fs (sdb1): re-mounted.
Opts: errors=remount-ro
Sep 20 12:03:52 muskatas kernel: [ 10.767575] EXT4-fs (sdb6): mounted
filesystem with ordered data mode. Opts: (null)
Sep 20 12:03:52 muskatas kernel: [ 10.781818] EXT4-fs (dm-1): mounted
filesystem with ordered data mode. Opts: (null)
Sep 20 12:03:52 muskatas kernel: [ 10.809712] EXT4-fs (dm-2): mounted
filesystem with ordered data mode. Opts: (null)
Sep 20 12:03:52 muskatas kernel: [ 10.874940] EXT4-fs (sdb3): mounted
filesystem with ordered data mode. Opts: (null)
Sep 20 12:03:52 muskatas kernel: [ 11.036904] systemd-udevd[1441]: failed
to execute '/lib/udev/socket:/org/freedesktop/hal/udev_event'
'socket:/org/freedesktop/hal/udev_event': No such file or directory
Sep 20 12:03:52 muskatas kernel: [ 11.126807] EXT4-fs (sdb2): mounted
filesystem with ordered data mode. Opts: (null)
Sep 20 12:03:52 muskatas kernel: [ 11.552037] EXT4-fs (dm-0): mounted
filesystem with ordered data mode. Opts: (null)
sdb1 is root, sdb2 is /usr, sdb3 is /var, dm-1 is /tmp.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371564
Title:
statd fails to come up on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1371564/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
