** Changed in: autofs5 (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007273
Title:
autofs does not start automatically after reboot
To manage
I'm following up on some old bugs today.
It sounds like this bug was upstart-specific. Since we are running
systemd now, it seems likely that this bug can be treated as fixed or
otherwise not relevant.
So I'll mark this Incomplete for now, until someone can please confirm
whether or not this
I'm a software developer, and my office uses NIS and autofs. Everyone
gets RHEL if I let my IT dept. installs, but I chose to install Ubuntu
Mate 14.04 LTS by myself.
I must tell you I'm having a hell of a time. First off, when I
misconfigured /etc/yp.conf, the upstart hangs. I had to boot up the
I'm a software developer, and my office uses NIS and autofs. Everyone
gets RHEL if I let my IT dept. installs, but I chose to install Ubuntu
Mate 14.04 LTS by myself.
I must tell you I'm having a hell of a time. First off, when I
misconfigured /etc/yp.conf, the upstart hangs. I had to boot up the
I've had this problem with every version of Ubuntu up to and including
15.04. Having a system that actually authenticates with NIS and allows
automounting when I log in always requires some kind of hack like this.
It's really annoying.
--
You received this bug notification because you are a
I've had this problem with every version of Ubuntu up to and including
15.04. Having a system that actually authenticates with NIS and allows
automounting when I log in always requires some kind of hack like this.
It's really annoying.
--
You received this bug notification because you are a
Today I installed 12.04.4 and all the above fixes didn't work on a
client machine.
Even if in some other thread (i think bug 958704) this was discouraged,
i added:
start wait-for-state WAIT_FOR=ypbind WAITER=autofs WAIT_STATE=running
after line 11 of /etc/init/autofs.conf, below the modprobe
Today I installed 12.04.4 and all the above fixes didn't work on a
client machine.
Even if in some other thread (i think bug 958704) this was discouraged,
i added:
start wait-for-state WAIT_FOR=ypbind WAITER=autofs WAIT_STATE=running
after line 11 of /etc/init/autofs.conf, below the modprobe
#13 contained the fix for me. commenting out the following gave ypbind
enough time to start so autofs correctly started as well
#if status ypbind | grep -q start/respawn; then
# # something killed ypbind; short-circuit here instead
# # of continuing to try to call ypwhich, since
#13 contained the fix for me. commenting out the following gave ypbind
enough time to start so autofs correctly started as well
#if status ypbind | grep -q start/respawn; then
# # something killed ypbind; short-circuit here instead
# # of continuing to try to call ypwhich, since
If the automounter daemon starts before the ypbind daemon is ready to
answer queries than the automounter does not work for nfs mounts
depending on nis (other mount types not tested), even if the ypbind
daemon later gets ready.
There exists a race condition in ubuntu 12.04 between autofs.conf
If the automounter daemon starts before the ypbind daemon is ready to
answer queries than the automounter does not work for nfs mounts
depending on nis (other mount types not tested), even if the ypbind
daemon later gets ready.
There exists a race condition in ubuntu 12.04 between autofs.conf
So, I took another look at this problem. autofs5's upstart script is
'start on runlevel [2345]. This just means start on runlevel 2 in
Ubuntu, because the others are not used.
Runlevel 2 is reached after all of the filesystems are mounted and any
interfaces in /etc/network/interfaces are up
So, I took another look at this problem. autofs5's upstart script is
'start on runlevel [2345]. This just means start on runlevel 2 in
Ubuntu, because the others are not used.
Runlevel 2 is reached after all of the filesystems are mounted and any
interfaces in /etc/network/interfaces are up
I have a similar issue, in my case it is related to ldap automount maps.
We ran into this same issue in 10.04 and ended up adding a condition in
the autofs upstart script to wait for a network connection, as well as
in the gdm (now lightdm) upstart script.
Bottom line is that the autofs startup
several people have commented that they have the same or similar
problems
** Changed in: autofs5 (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
I have a similar issue, in my case it is related to ldap automount maps.
We ran into this same issue in 10.04 and ended up adding a condition in
the autofs upstart script to wait for a network connection, as well as
in the gdm (now lightdm) upstart script.
Bottom line is that the autofs startup
several people have commented that they have the same or similar
problems
** Changed in: autofs5 (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007273
I encountered exactly the same issue encountered by Kevin including the
contents of the log files, and worked around it the same way he did.
Thanks, Kevin!
In my case NIS servers are not local. Could that have caused ypbind to
get backgrounded?
Though that doesn't explain why it binds fine with
The issue seems to revolve around the upstart scripts, I attempted to
rewrite sections of the scripts so that the service would start at later
(higher) run level but to no effect. The issue is not with DNS
resolution of the domain though. Something is wrong when network-manager
initializes the
The issue seems to revolve around the upstart scripts, I attempted to
rewrite sections of the scripts so that the service would start at later
(higher) run level but to no effect. The issue is not with DNS
resolution of the domain though. Something is wrong when network-manager
initializes the
I encountered exactly the same issue encountered by Kevin including the
contents of the log files, and worked around it the same way he did.
Thanks, Kevin!
In my case NIS servers are not local. Could that have caused ypbind to
get backgrounded?
Though that doesn't explain why it binds fine with
I was able to circumvent this issue by removing the network-manager
package and managing devices manually.
--
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
I was able to circumvent this issue by removing the network-manager
package and managing devices manually.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007273
Title:
autofs does not start
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
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
This problem is fixed now. Seems like dnsmasq is started this way jet,
making sure it starts before any other service depending on dns is
started.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
Thanks Thomas, so does that mean that the bug is solved for you?
--
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
This problem is fixed now. Seems like dnsmasq is started this way jet,
making sure it starts before any other service depending on dns is
started.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007273
Thanks Thomas, so does that mean that the bug is solved for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007273
Title:
autofs does not start automatically after reboot
To manage
Thomas, with Ubuntu 11.10 and later, there is a guarantee that all of
the auto interfaces have been brought up before runlevel 2 is reached
(or after 2 minutes of waiting for said interfaces has passed). This is
controlled by if-up.d scripts, which are only called after the interface
has been
Thomas, with Ubuntu 11.10 and later, there is a guarantee that all of
the auto interfaces have been brought up before runlevel 2 is reached
(or after 2 minutes of waiting for said interfaces has passed). This is
controlled by if-up.d scripts, which are only called after the interface
has been
Yes, I can confirm my servers setup doesn't use network manager or conman.
Sometimes autofs is started, sometimes it is not. It seems to depend on how
fast the network interfaces are up – if they are up before autofs tries to get
names resolved by DNS all is OK and autofs starts. If not, it
Yes, I can confirm my servers setup doesn't use network manager or conman.
Sometimes autofs is started, sometimes it is not. It seems to depend on how
fast the network interfaces are up – if they are up before autofs tries to get
names resolved by DNS all is OK and autofs starts. If not, it
Hi Thomas.
been b
autofs5 starts when runlevel 2 is reached.
This means that it starts after any network connections that are
configured in /etc/network/interfaces have been brought up. That would
include DNS configurations of any kind that a server would have.
If, however, you have configured
Hi Thomas.
been b
autofs5 starts when runlevel 2 is reached.
This means that it starts after any network connections that are
configured in /etc/network/interfaces have been brought up. That would
include DNS configurations of any kind that a server would have.
If, however, you have configured
36 matches
Mail list logo
