Public bug reported:
autofs 5.0.7-3ubuntu3.1 installs *both* /etc/init/autofs.conf and
/etc/init.d/autofs. (One wonders what this duplication is needed for.)
It is apparently possible for /etc/init.d/autofs start to be run before
Upstart decides to act on /etc/init/autofs.conf. When this happens on my
systems,
1) there is an automount instance running and its PID can be found in
/run/autofs.pid (this is OK);
2) "service autofs status" prints "autofs stop/waiting" and returns exit code 0;
3) my Puppet configuration, which contains a "service { autofs: ensure =>
running }" or equivalent somewhere, causes noisy attempts by Upstart to restart
the autofs service (which fails since the service is already running).
Eventually these result in an "init: autofs respawning too fast, stopped"
message in the logs (until the next puppet run).
About point 2), I'll note that "/etc/init.d/autofs status" correctly
prints " * automount is running". However, the presence of
/etc/init/autofs.conf results in the official tools (/usr/sbin/service,
/usr/sbin/invoke-rc.d) ignoring /etc/init.d/autofs status.
I have a hunch that the solution to this bug will be to remove
/etc/init.d/autofs from the Ubuntu autofs package; is there any good
reason not to do so?
** Affects: autofs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1403646
Title:
/etc/init.d/autofs confuses upstart
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1403646/+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
