Comment 16 for bug 573919

Revision history for this message
Carl Nobile (cnobile1) wrote : Re: autofs doesn't work with lucid

If you look in /etc/init/portmap.conf you will see that its prerequisite for starting is statd which is done in /etc/init/portmap.conf. However, there are numerous errors in my /var/log/boot.log file.

I upgraded two machines and both have the same issue as mentioned above. A new install I did does not have this issue, so it obviously is some config issues that is going badly when upgrading.

I was originally fixing this issue by stopping then starting portmap again. (A restart didn't work.)

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