On Mon, Oct 15, 2012 at 12:44:16PM -0000, 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 access to your puppetmaster setup. It looks like this is the only thing that is different. I tested the behaviour without connecting to a puppetmaster at all, since the agent appears to happily run even if it cannot connect to one. Can you try this, perhaps? Are you sure that your puppet manifests aren't accidentally changing puppet's own startup scripts or configuration in a way that is causing this? -- 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