After 5 more reboots the at method failed. More exploration showed that status statd
could show "start/running" and rpcinfo -p | grep status could show both the tcp and udp ports, and a couple of wait seconds could be put in there, and it could be run from an at command and even then killall -SIGUSR1 mountall would sometimes fail to respond to the signal. So I figured that perhaps statd was in a funky state too. Reset all the /etc/init files to their original values and put in rc.local and saf2.sh (the next two attachments). Have now booted 10 consecutive times with NSF mounts connected once I login. Of these 8 still had the statd error messages, but at least this hack finally made them mount in the end. Here is what shows up in the message.log when this happens: Aug 26 09:54:30 saf04 logger: NFSGLITCH marunning [ root 391 1 0 09:54 ? 00:00:00 mountall --daemon ] Aug 26 09:54:30 saf04 logger: NFSGLITCH use at to kill mountall Aug 26 09:54:31 saf04 logger: NFSGLITCH2 statd: CLAIMS to be in start/running, restart it anyway Aug 26 09:54:32 saf04 logger: NFSGLITCH2 marunning? [ root 391 1 1 09:54 ? 00:00:00 mountall --daemon ] Aug 26 09:54:32 saf04 logger: NFSGLITCH2 trying sigusr1 on mountall from at job Aug 26 09:54:32 saf04 kernel: [ 20.298991] RPC: Registered udp transport module. Aug 26 09:54:32 saf04 kernel: [ 20.298994] RPC: Registered tcp transport module. Aug 26 09:54:32 saf04 kernel: [ 20.298995] RPC: Registered tcp NFSv4.1 backchannel transport module. Aug 26 09:54:33 saf04 logger: NFSGLITCH2 kstat 0 marunning STILL? [ ] -- mountall for /var races with rpc.statd https://bugs.launchpad.net/bugs/525154 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
