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

[Marius Gedminas]

I've just noticed

    init: portmap main process (1198) terminated with status 127
    init: portmap main process ended, respawning
    init: portmap post-start process (1202) terminated with status 1

in /var/log/syslog, about half a second before statd's startup failures.
This might explain them.

Again, no indication why portmap would fail.  There's no
/var/log/upstart/portmap.log.  When I ssh in after boot, 'status
portmap' shows 'start/running'.  /var/log/boot.log says

     * Starting Upstart job to start rpcbind on boot only[ OK ]
     * Starting Upstart job to start portmap on boot only[ OK ]
     * Stopping Upstart job to start rpcbind on boot only[ OK ]
     * Stopping Upstart job to start portmap on boot only[ OK ]
     * Stopping Mount network filesystems[ OK ]
     * Starting Bridge socket events into upstart[ OK ]
     * Starting RPC port mapper[ OK ]
     * Starting RPC portmapper replacement[ OK ]
     * Starting NSM status monitor[ OK ]
     * Starting NSM status monitor[ OK ]
     * Starting NSM status monitor[ OK ]
     * Starting NSM status monitor[ OK ]
     * Starting NSM status monitor[ OK ]
     * Starting NSM status monitor[ OK ]
     * Starting NSM status monitor[ OK ]
     * Starting NSM status monitor[ OK ]
     * Starting NSM status monitor[ OK ]
     * Starting NSM status monitor[ OK ]
     * Starting NSM status monitor[ OK ]
     * Starting NSM status monitor[fail]
     * Stopping NSM status monitor[ OK ]

which indicates no portmap failures, although it's a bit strange to see
both 'RPC port mapper' and 'RPC portmapper replacement' both.

(This server is running Ubuntu since 7.10, who knows what obsolete
packages/config files might have accumulated during all those upgrades.)

-- 
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