I was browsing the group to see if anyone else was experiencing the issue. I'm having the same with CentOS 6.2 x86_64. From what I see, puppetd should be running with the user puppet. However, the pid is now owned by root, which is obviously the issue. Someone made a mistake on the puppet RPM spec somewhere.
On Jan 26, 4:00 am, Steph Gosling <[email protected]> wrote: > Hi all, > > Upgraded a master and a couple of clients to 2.7.10 and now see the > following when running an agent if the daemon is also running: > > [steph@somehost ~]$ sudo puppet agent --onetime --verbose --no-daemonize > info: Caching catalog for somehost.example.com > info: Applying configuration version '1327578407' > notice: /Stage[main]/Mysql-server/Package[mysql-server]/ensure: created > notice: /Stage[main]/Mysql-server/Service[mysqld]/ensure: ensure changed > 'stopped' to 'running' > notice: Finished catalog run in 20.11 seconds > err: Could not remove PID file /var/run/puppet/agent.pid > [steph@somehost ~]$ > > I see that 2.7.10 fixed a bughttp://projects.puppetlabs.com/issues/5246and > wonder if they're > related? > > in 2.7.9 this would run without throwing the error, indeed in .10 the > onetime run completes and the agent daemon is happy too: It's just > unnerving to see pink messages :) Environment is CentOS > 6.2 fwiw. > > -- > Steph Gosling <[email protected]> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
