** Changed in: puppet (Ubuntu)
Status: Incomplete = Invalid
--
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
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I have not managed to reproduce this on Precise using puppet
2.7.11-1ubuntu2.1.
When I start puppet using /etc/init.d/puppet start, I get
/var/run/puppet/agent.pid. When I stop it using /etc/init.d/puppet
stop,
After a clean install i type
#apt-get install puppet
following which i change the line in /etc/default/puppet from START=no to
START=yes
then i join the puppet client to my puppet server using
#puppetd --server servername --waitforcert 60 --test
on the client side and
#puppetca --sign
On Mon, Oct 15, 2012 at 12:44:16PM -, Matthew Malkin wrote:
I assume in this case ${NAME} resolves to puppet
${NAME} is set directly in the init script, two lines above, to agent.
Do you see this in your init script too?
Unfortunately I can't reproduce your setup exactly since I don't have
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}
Strange
Unfortunately I didn't keep the instance of the VM I just got those
results above from.
Having just recreated the VM (always from a snapshot of 12.04.1 before
first boot but after installation) following the same steps and before I
connected it to the puppetmaster i tested and it worked
Matthew Malkin 1060...@bugs.launchpad.net writes:
Indeed the only difference between the two files is one (the one
installed by the puppetmaster) has PIDFILE=/var/run/puppet/agent.pid
and the other (before puppetmaster changed it) had
/var/run/puppet/${NAME}.pid (difference tracked with
Oh, i forgot to mention. I discovered this bug on a server, and then to
confirm i set up a clean install of ubuntu server (same version) in
virtualbox and it shows the same problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
