Matthew Malkin <1060...@bugs.launchpad.net> writes:
> the reason appears to be because the /etc/init.d/puppet file contains the
> line:
> PIDFILE="/var/run/puppet/${NAME}.pid"
> I assume in this case ${NAME} resolves to "puppet"
[...]
> Simply changing the line in the /etc/init.d/puppet file from "${NAME}"
> to "agent" should (and does) solve the problem
There is no need to assume, that is set explicitly in the init script.
What does the command 'grep ^NAME /etc/init.d/puppet' give as output in
your case?
In the debian packaging, it was set to "puppetd" in 0.25.5-1, but
changed to "agent" in 2.6.0-1. For the ubuntu packaging, it may be
different.
Your bug report mentions a newer version, could you check if you have
the init script that came with the package, or if it is changed, or an
older version is kept when upgrading? An "md5sum /etc/init.d/puppet" may
also help, if they differ.
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1060184
Title:
puppet client init script pid file error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1060184/+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
