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
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
