[Bug 1371564] Re: statd incompatible with /var as a separate filesystem
Maciej Puzio
1371564 at bugs.launchpad.net
Tue Jun 2 22:07:37 UTC 2015
For a system with a separate /var partition, the workaround from year 2010 appears to work:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/525154/comments/8
For the Ubuntu 14.04 this workaround translates to:
--- /etc/init/statd.conf.ORIG 2013-09-11 16:46:50.000000000 -0500
+++ etc/init/statd.conf 2015-06-02 16:24:42.029659358 -0500
@@ -12,7 +12,7 @@
# TYPE=nfs is handled in the "statd-mounting" job.
#
start on (started portmap ON_BOOT=
- or (virtual-filesystems and started portmap ON_BOOT=y))
+ or (virtual-filesystems and mounted MOUNTPOINT=/var and started portmap ON_BOOT=y))
stop on stopping portmap
expect fork
--
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 incompatible with /var as a separate filesystem
Status in nfs-utils package in Ubuntu:
Triaged
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
More information about the foundations-bugs
mailing list