Steph Gosling
2012-Jan-26 12:00 UTC
[Puppet Users] Anyone seeing odd agent behaviour with 2.7.10?
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 bug http://projects.puppetlabs.com/issues/5246 and 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 <steph@chuci.org> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Jonathan Gazeley
2012-Jan-26 12:26 UTC
Re: [Puppet Users] Anyone seeing odd agent behaviour with 2.7.10?
I am seeing the same message printed on each run, on CentOS 6.2. Puppet still works, so it''s not critical. Just waiting for a fix :) Jonathan On 26/01/12 12:00, Steph Gosling 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 bug > http://projects.puppetlabs.com/issues/5246 and 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. > > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Steph Gosling
2012-Jan-26 12:36 UTC
Re: [Puppet Users] Anyone seeing odd agent behaviour with 2.7.10?
Yeah everything does work, I just really don''t like seeing pink :) Cheers, Steph On Thu, 26 Jan 2012 12:26:14 +0000 Jonathan Gazeley <jonathan.gazeley@bristol.ac.uk> wrote:> I am seeing the same message printed on each run, on CentOS 6.2. Puppet > still works, so it''s not critical. Just waiting for a fix :) > > Jonathan > > > On 26/01/12 12:00, Steph Gosling 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 bug > > http://projects.puppetlabs.com/issues/5246 and 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. > > > > > > > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- Steph Gosling <steph@chuci.org> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
R.I.Pienaar
2012-Jan-26 12:53 UTC
Re: [Puppet Users] Anyone seeing odd agent behaviour with 2.7.10?
Looks like the code paths in Puppet::Agent changed a lot and the patch that was applied and worked for 2.6.x would need to be different for 2.7.x Will set up a 2.7 master and see if i can reproduce/fix ----- Original Message -----> Yeah everything does work, I just really don''t like seeing pink :) > > Cheers, > > Steph > > On Thu, 26 Jan 2012 12:26:14 +0000 > Jonathan Gazeley <jonathan.gazeley@bristol.ac.uk> wrote: > > > I am seeing the same message printed on each run, on CentOS 6.2. > > Puppet > > still works, so it''s not critical. Just waiting for a fix :) > > > > Jonathan > > > > > > On 26/01/12 12:00, Steph Gosling 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 bug > > > http://projects.puppetlabs.com/issues/5246 and 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. > > > > > > > > > > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscribe@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en. > > > > > -- > Steph Gosling <steph@chuci.org> > > -- > You received this message because you are subscribed to the Google > Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- R.I.Pienaar -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
R.I.Pienaar
2012-Jan-26 13:07 UTC
Re: [Puppet Users] Anyone seeing odd agent behaviour with 2.7.10?
On a fresh 2.7.10 install with official RPMs on CentOS 6.2 I can''t reproduce this: [root@dev1]# puppet agent --onetime --verbose --no-daemonize info: Caching catalog for dev1.devco.net info: Applying configuration version ''1327583153'' notice: Finished catalog run in 0.28 seconds [root@dev1]# and if i run it without the --no-daemonize it creates its pid and removes it when its done - didnt do that before ----- Original Message -----> Looks like the code paths in Puppet::Agent changed a lot and the > patch > that was applied and worked for 2.6.x would need to be different for > 2.7.x > > Will set up a 2.7 master and see if i can reproduce/fix > > ----- Original Message ----- > > Yeah everything does work, I just really don''t like seeing pink :) > > > > Cheers, > > > > Steph > > > > On Thu, 26 Jan 2012 12:26:14 +0000 > > Jonathan Gazeley <jonathan.gazeley@bristol.ac.uk> wrote: > > > > > I am seeing the same message printed on each run, on CentOS 6.2. > > > Puppet > > > still works, so it''s not critical. Just waiting for a fix :) > > > > > > Jonathan > > > > > > > > > On 26/01/12 12:00, Steph Gosling 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 bug > > > > http://projects.puppetlabs.com/issues/5246 and 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. > > > > > > > > > > > > > > > > > > -- > > > You received this message because you are subscribed to the > > > Google > > > Groups "Puppet Users" group. > > > To post to this group, send email to > > > puppet-users@googlegroups.com. > > > To unsubscribe from this group, send email to > > > puppet-users+unsubscribe@googlegroups.com. > > > For more options, visit this group at > > > http://groups.google.com/group/puppet-users?hl=en. > > > > > > > > > -- > > Steph Gosling <steph@chuci.org> > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscribe@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en. > > > > > > -- > R.I.Pienaar > > -- > You received this message because you are subscribed to the Google > Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- R.I.Pienaar -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Steph Gosling
2012-Jan-26 13:10 UTC
Re: [Puppet Users] Anyone seeing odd agent behaviour with 2.7.10?
Is the puppet agent daemon running when you run the agent by hand? On Thu, 26 Jan 2012 13:07:16 +0000 (GMT) "R.I.Pienaar" <rip@devco.net> wrote:> On a fresh 2.7.10 install with official RPMs on CentOS 6.2 I can''t reproduce this: > > [root@dev1]# puppet agent --onetime --verbose --no-daemonize > info: Caching catalog for dev1.devco.net > info: Applying configuration version ''1327583153'' > notice: Finished catalog run in 0.28 seconds > [root@dev1]# > > and if i run it without the --no-daemonize it creates its pid and removes > it when its done - didnt do that before > > > > ----- Original Message ----- > > Looks like the code paths in Puppet::Agent changed a lot and the > > patch > > that was applied and worked for 2.6.x would need to be different for > > 2.7.x > > > > Will set up a 2.7 master and see if i can reproduce/fix > > > > ----- Original Message ----- > > > Yeah everything does work, I just really don''t like seeing pink :) > > > > > > Cheers, > > > > > > Steph > > > > > > On Thu, 26 Jan 2012 12:26:14 +0000 > > > Jonathan Gazeley <jonathan.gazeley@bristol.ac.uk> wrote: > > > > > > > I am seeing the same message printed on each run, on CentOS 6.2. > > > > Puppet > > > > still works, so it''s not critical. Just waiting for a fix :) > > > > > > > > Jonathan > > > > > > > > > > > > On 26/01/12 12:00, Steph Gosling 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 bug > > > > > http://projects.puppetlabs.com/issues/5246 and 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. > > > > > > > > > > > > > > > > > > > > > > > -- > > > > You received this message because you are subscribed to the > > > > Google > > > > Groups "Puppet Users" group. > > > > To post to this group, send email to > > > > puppet-users@googlegroups.com. > > > > To unsubscribe from this group, send email to > > > > puppet-users+unsubscribe@googlegroups.com. > > > > For more options, visit this group at > > > > http://groups.google.com/group/puppet-users?hl=en. > > > > > > > > > > > > > -- > > > Steph Gosling <steph@chuci.org> > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Puppet Users" group. > > > To post to this group, send email to puppet-users@googlegroups.com. > > > To unsubscribe from this group, send email to > > > puppet-users+unsubscribe@googlegroups.com. > > > For more options, visit this group at > > > http://groups.google.com/group/puppet-users?hl=en. > > > > > > > > > > -- > > R.I.Pienaar > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscribe@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en. > > > > > > -- > R.I.Pienaar > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- Steph Gosling <steph@chuci.org> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
R.I.Pienaar
2012-Jan-26 13:14 UTC
Re: [Puppet Users] Anyone seeing odd agent behaviour with 2.7.10?
----- Original Message -----> Is the puppet agent daemon running when you run the agent by hand?Ah! thats it, I''ll take a look -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Ashley Penney
2012-Jan-26 14:46 UTC
Re: [Puppet Users] Anyone seeing odd agent behaviour with 2.7.10?
I''m having the same thing, I use puppetd -tv all the time and now it''s trying to delete a .pid at the end: err: Could not remove PID file /var/run/puppet/agent.pid It''s super annoying but not fatal I suppose. I stopped the daemon from running and tried running puppetd again but it still gave the same error. On Thu, Jan 26, 2012 at 8:14 AM, R.I.Pienaar <rip@devco.net> wrote:> > > ----- Original Message ----- > > Is the puppet agent daemon running when you run the agent by hand? > > > Ah! thats it, I''ll take a look > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
R.I.Pienaar
2012-Jan-26 14:48 UTC
Re: [Puppet Users] Anyone seeing odd agent behaviour with 2.7.10?
----- Original Message -----> I''m having the same thing, I use puppetd -tv all the time and now > it''s > trying to delete a .pid at the end: > > > err: Could not remove PID file /var/run/puppet/agent.pid > > > It''s super annoying but not fatal I suppose. I stopped the daemon > from running and tried running puppetd again but it still gave the same > error.that''s weird, did the daemon leave behind a pid file or somethign? my testing werent showing this error when the daemon wasnt running. anyway, opened https://projects.puppetlabs.com/issues/12188 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Will S. G.
2012-Feb-10 23:14 UTC
[Puppet Users] Re: Anyone seeing odd agent behaviour with 2.7.10?
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 <st...@chuci.org> 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 <st...@chuci.org>-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Craig White
2012-Feb-10 23:38 UTC
Re: [Puppet Users] Re: Anyone seeing odd agent behaviour with 2.7.10?
to my knowledge puppetd always runs as root because it needs the permissions in order to perform its magic. puppetmaster runs as user:puppet, group:puppet but not puppetd Craig On Feb 10, 2012, at 4:14 PM, Will S. G. wrote:> 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 <st...@chuci.org> 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 <st...@chuci.org> > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white@ttiltd.com 1.800.869.6908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ www.ttiassessments.com Need help communicating between generations at work to achieve your desired success? Let us help! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Michael Stahnke
2012-Feb-12 18:08 UTC
Re: [Puppet Users] Re: Anyone seeing odd agent behaviour with 2.7.10?
On Fri, Feb 10, 2012 at 3:38 PM, Craig White <craig.white@ttiltd.com> wrote:> to my knowledge puppetd always runs as root because it needs the permissions in order to perform its magic. > puppetmaster runs as user:puppet, group:puppet but not puppetdThat is correct. There is a fix for this in 2.7.x and will be in the 2.7.11rc which should be out next week.> > Craig > > On Feb 10, 2012, at 4:14 PM, Will S. G. wrote: > >> 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 <st...@chuci.org> 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 <st...@chuci.org> >> >> -- >> You received this message because you are subscribed to the Google Groups "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >> > > -- > Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white@ttiltd.com > 1.800.869.6908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ www.ttiassessments.com > > Need help communicating between generations at work to achieve your desired success? Let us help! > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.