This seems to be the same bug as in 573919 where statd is not started. If you look in /etc/init/portmap.conf you will see that its prerequisite for starting is statd which must have been started when I used one of the two methods mentiond above to restart portmap.
I have found this in my /var/log/boot.log file: init: statd main process (730) terminated with status 1 init: statd main process ended, respawning init: statd main process (736) terminated with status 1 init: statd main process ended, respawning init: statd main process (747) terminated with status 1 init: statd main process ended, respawning init: statd main process (754) terminated with status 1 init: statd main process ended, respawning init: rpc_pipefs pre-start process (703) terminated with status 32 init: statd main process (764) terminated with status 1 init: statd main process ended, respawning init: statd main process (770) terminated with status 1 init: statd main process ended, respawning init: statd main process (776) terminated with status 1 init: statd main process ended, respawning init: statd main process (782) terminated with status 1 init: statd main process ended, respawning init: statd main process (788) terminated with status 1 init: statd main process ended, respawning init: statd main process (794) terminated with status 1 init: statd main process ended, respawning init: statd main process (800) terminated with status 1 init: statd respawning too fast, stopped I will continue posting in the 573919 thread since this seems to be the same bug. -- After boot/logout portmap needs to be reconfigured and restarted https://bugs.launchpad.net/bugs/590570 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
