Public bug reported:
When restarting the puppetmaster process (via the service command, or
calling the initscript directly), the restart can fail if the original
process does not exit immediately. This is because the initscript is not
written to wait for the original process to exit.
In my testing under Trusty, adding "-R n" to the start-stop-daemon
command in the initscript fixed the problem. It's difficult to determine
an appropriate value for n, but it could be tunable via
/etc/default/puppetmaster. It's definitely a problem not to wait at all
for the process to exit.
** Affects: puppetmaster (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- When the puppetmaster process (via the service command, or calling the
- initscript directly), the restart can fail if the original process does
- not exit immediately. This is because the initscript is not written to
- wait for the original process to exit.
+ When restarting the puppetmaster process (via the service command, or
+ calling the initscript directly), the restart can fail if the original
+ process does not exit immediately. This is because the initscript is not
+ written to wait for the original process to exit.
In my testing, adding "-R n" to the start-stop-daemon command in the
initscript fixed the problem. It's difficult to determine an appropriate
value for n, but it could be tunable via /etc/default/puppetmaster. It's
definitely a problem not to wait at all for the process to exit.
** Description changed:
When restarting the puppetmaster process (via the service command, or
calling the initscript directly), the restart can fail if the original
process does not exit immediately. This is because the initscript is not
written to wait for the original process to exit.
- In my testing, adding "-R n" to the start-stop-daemon command in the
- initscript fixed the problem. It's difficult to determine an appropriate
- value for n, but it could be tunable via /etc/default/puppetmaster. It's
- definitely a problem not to wait at all for the process to exit.
+ In my testing under Trusty, adding "-R n" to the start-stop-daemon
+ command in the initscript fixed the problem. It's difficult to determine
+ an appropriate value for n, but it could be tunable via
+ /etc/default/puppetmaster. It's definitely a problem not to wait at all
+ for the process to exit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315021
Title:
Service restart fails because process has not exited
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppetmaster/+bug/1315021/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
