Not disputing that it's a real problem, just saying that rc.local doesn't get us closer to understanding it :)
> Apparently id doesn't resolve 192.168.88.252 (?) This just means that mountall first tried to mount the share before the network was fully up. This is perfectly normal; and as you can see, it tries again later in the log and gets a different error... specifically the statd error. Is there any chance you can test this with a daily build of the 12.04 server? 12.04 has support for better logging of upstart jobs, which would enable us to see whether something is causing statd to fail to start on boot. The way this is supposed to work is that /etc/init/statd-mounting.conf should trigger as soon as mountall tries to mount the nfs share, and this will block the mount attempt while trying to start the statd job, which in turn launches portmap and waits for it to come up before running rpc.statd. This has all shown itself to be rather reliable since 11.04 when it landed, so I don't know what's causing the problem in your case... we're really going to need some logging to figure it out. ** Package changed: mountall (Ubuntu) => nfs-utils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933575 Title: NFS not being mounted at boot time - rpc.statd is not running but is required for remote locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/933575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
