[Bug 511245] Re: portmap is not started during boot process before autofs and hence autofs does not work properly

2010-06-14 Thread Pat Double
I'm not sure if this is related, but my problem is similar except that statd is not starting and so autofs breaks. It was working over a week ago. -- portmap is not started during boot process before autofs and hence autofs does not work properly https://bugs.launchpad.net/bugs/511245 You

[Bug 511245] Re: portmap is not started during boot process before autofs and hence autofs does not work properly

2010-04-26 Thread Gürkan Sengün
Absolutely, this should be fixed for any stable release, not just LTS. -- portmap is not started during boot process before autofs and hence autofs does not work properly https://bugs.launchpad.net/bugs/511245 You received this bug notification because you are a member of Ubuntu Server Team,

[Bug 511245] Re: portmap is not started during boot process before autofs and hence autofs does not work properly

2010-04-12 Thread Thag
I'd like to bump the priority on this as it makes it impossible for servers to come up clean. For an LTS release, I would expect that having servers boot clean would be a priority. -- portmap is not started during boot process before autofs and hence autofs does not work properly

[Bug 511245] Re: portmap is not started during boot process before autofs and hence autofs does not work properly

2010-04-12 Thread Thag
Gets worse if you add SAN volumes that are NFS exported. There's a corner case here that's not working at all: 1 - QLogic SAN - Fails to come up until I reload qla driver with modprobe -r/modprobe 2 - NFS export, since #1 didn't come up, export also fails. 3 - Since #2 didn't come up, autofs

[Bug 511245] Re: portmap is not started during boot process before autofs and hence autofs does not work properly

2010-03-17 Thread Ralph Janke
Since portmap is now started by upstart, it makes more sense to port autofs over to upstart too and trigger the start on the event of portmap being started. -- portmap is not started during boot process before autofs and hence autofs does not work properly https://bugs.launchpad.net/bugs/511245

[Bug 511245] Re: portmap is not started during boot process before autofs and hence autofs does not work properly

2010-03-17 Thread Cédric Dufour
The problem is the same for NIS: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/119660 I do agree that porting autofs to upstart would be ideal. Unfortunately, it seems it requires a good knowledge of Ubuntu's upstart events chain to do it properly. Maybe someone knowledgeable enough with

[Bug 511245] Re: portmap is not started during boot process before autofs and hence autofs does not work properly

2010-03-17 Thread Cédric Dufour
After a few reboot, it seems I found the quick-'n-elegant fix for that issue: r...@lucid-golden:~ # cat /etc/init/autofs-ldap.conf # Restart AutoFS-LDAP after everything has settled start on (stopped networking and stopped rc RUNLEVEL=[2345]) exec /etc/init.d/autofs restart Problem with

[Bug 511245] Re: portmap is not started during boot process before autofs and hence autofs does not work properly

2010-03-11 Thread Cédric Dufour
I'm experiencing the (same?) problem with Lucid (and autofs-ldap). After rebooting, one time it works... another time not (until autofs is manually restarted) That does sound like an upstart race condition. Unfortunately, this is quite important for enterprise environments :-( I guess at the time

[Bug 511245] Re: portmap is not started during boot process before autofs and hence autofs does not work properly

2010-01-26 Thread Chuck Short
This looks like an upstart race to me. Ill try to get this fixed for lucid. Regards chuck ** Changed in: autofs (Ubuntu) Importance: Undecided = Low ** Changed in: autofs (Ubuntu) Status: New = Triaged -- portmap is not started during boot process before autofs and hence autofs does