I have encountered this too while trying to put together an image for 12.04.1 LTS kernel 3.2.0-31-generic. Same premise, upstart fails to correctly initialize autofs (5.0.6-0ubuntu5) on boot because of ypbind wait-for-state issues but it doesn't seem to be related to dnsmasq (server is NOT managed by NM). It works after the autofs service is reset/reloaded post-boot. Here are my logs,
Some Interesting stuff in the boot log: fsck from util-linux 2.20.1 fsck from util-linux 2.20.1 rpcbind: Cannot open '/run/rpcbind/rpcbind.xdr' file for reading, errno 2 (No such file or directory) rpcbind: Cannot open '/run/rpcbind/portmap.xdr' file for reading, errno 2 (No such file or directory) /dev/sda6: clean, 172583/61014016 files, 4655506/244044544 blocks /dev/sda1: clean, 230/121920 files, 50217/487424 blocks Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd * Starting AppArmor profiles [ OK ] speech-dispatcher disabled; edit /etc/default/speech-dispatcher * Starting VirtualBox kernel modules [ OK ] * Starting Waiting for state [ OK ] * VirtualBox Additions disabled, not in a Virtual Machine * Starting mDNS/DNS-SD daemon [ OK ] saned disabled; edit /etc/default/saned * Starting bluetooth daemon [ OK ] * Starting crash report submission daemon [ OK ] * Starting network connection manager [ OK ] * Checking battery state... [ OK ] * Starting CUPS printing spooler/server [ OK ] * Stopping System V runlevel compatibility [ OK ] * Starting NIS binding process [ OK ] * Stopping Waiting for state [ OK ] * Stopping Waiting for state [ OK ] * Stopping Waiting for state [ OK ] * Stopping block processes that need ypbind [ OK ] * Stopping block processes that need ypbind [ OK ] * Stopping block processes that need ypbind [ OK ] * Starting LightDM Display Manager [ OK ] * Starting deferred execution scheduler [ OK ] /var/log/syslog | grep autofs Sep 25 17:16:31 $HOSTNAME kernel: [ 17.471221] init: wait-for-state (autofsypbind) main process (1103) killed by TERM signal /var/log/upstart/wait-for-state-autofsypbind.log && /var/log/upstart/wait-for-state-atdypbind && /var/log/upstart/wait-for-state-lightdmypbind.log start: Job is already running: ypbind /var/log/upstart/ypbind Setting NIS domainname to: $NIS_DOMAIN Binding to YP server .....backgrounded Setting NIS domainname to: $NIS_DOMAIN Binding to YP server .....backgrounded /var/log/upstart/start-ypbind-autofs.log wait-for-state stop/waiting wait-for-state stop/waiting wait-for-state stop/waiting -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/1007273 Title: autofs does not start automatically after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1007273/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
