[Bug 1371564] Re: statd fails to come up on boot

[Marius Gedminas]

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
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1371564

Title:
  statd fails to come up on boot

Status in “nfs-utils” package in Ubuntu:
  Incomplete

Bug description:
  I've a server that stubbornly doesn't mount NFS filesystems on boot.
  I upgraded it to 14.04 and the problem persists.  This time I dug
  deeper and discovered that the mount upstart jobs are blocked waiting
  for statd-mounting, which are waiting for statd to come up, but statd
  is in "stop/waiting" state and doesn't want to come up.

  /var/log/syslog shows

      Sep 19 12:21:58 muskatas kernel: [    9.356501] init: statd main process (1268) terminated with status 1
      Sep 19 12:21:58 muskatas kernel: [    9.356511] init: statd main process ended, respawning
      Sep 19 12:21:58 muskatas kernel: [    9.363809] init: statd main process (1272) terminated with status 1
      Sep 19 12:21:58 muskatas kernel: [    9.363819] init: statd main process ended, respawning
      Sep 19 12:21:58 muskatas kernel: [    9.370785] init: statd main process (1276) terminated with status 1
      Sep 19 12:21:58 muskatas kernel: [    9.370795] init: statd main process ended, respawning
      Sep 19 12:21:58 muskatas kernel: [    9.382239] init: statd main process (1281) terminated with status 1
      Sep 19 12:21:58 muskatas kernel: [    9.382250] init: statd main process ended, respawning
      Sep 19 12:21:58 muskatas kernel: [    9.394097] init: statd main process (1285) terminated with status 1
      Sep 19 12:21:58 muskatas kernel: [    9.394107] init: statd main process ended, respawning
      Sep 19 12:21:58 muskatas kernel: [    9.400026] init: statd main process (1289) terminated with status 1
      Sep 19 12:21:58 muskatas kernel: [    9.400037] init: statd main process ended, respawning
      Sep 19 12:21:58 muskatas kernel: [    9.411247] init: statd main process (1293) terminated with status 1
      Sep 19 12:21:58 muskatas kernel: [    9.411258] init: statd main process ended, respawning
      Sep 19 12:21:58 muskatas kernel: [    9.421803] init: statd main process (1297) terminated with status 1
      Sep 19 12:21:58 muskatas kernel: [    9.421813] init: statd main process ended, respawning
      Sep 19 12:21:58 muskatas kernel: [    9.429929] init: statd main process (1302) terminated with status 1
      Sep 19 12:21:58 muskatas kernel: [    9.429939] init: statd main process ended, respawning
      Sep 19 12:21:58 muskatas kernel: [    9.442795] init: statd main process (1306) terminated with status 1
      Sep 19 12:21:58 muskatas kernel: [    9.442805] init: statd main process ended, respawning
      Sep 19 12:21:58 muskatas kernel: [    9.457698] init: statd main process (1310) terminated with status 1
      Sep 19 12:21:58 muskatas kernel: [    9.457708] init: statd respawning too fast, stopped

  If I 'sudo start statd' after logging in, the statd-mounting jobs are
  terminated and mountall proceeds to mount the NFS filesystems.

  I'm not sure how to debug this further.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1371564/+subscriptions