Anyone seeing odd agent behaviour with 2.7.10?

[Steph Gosling]

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 <st...@chuci.org>

[Jonathan Gazeley]

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

[Steph Gosling]

Yeah everything does work, I just really don't like seeing pink :)

Cheers,

Steph

> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>

--
Steph Gosling <st...@chuci.org>

[R.I.Pienaar]

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

--
R.I.Pienaar

[R.I.Pienaar]

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

[Steph Gosling]

Is the puppet agent daemon running when you run the agent by hand?

[R.I.Pienaar]

----- Original Message -----
> Is the puppet agent daemon running when you run the agent by hand?

Ah! thats it, I'll take a look

[Ashley Penney]

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.

[R.I.Pienaar]

----- 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

[Will S. G.]

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

[Craig White]

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

> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>

--
Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig...@ttiltd.com
1.800.869.6908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ www.ttiassessments.com

Need help communicating between generations at work to achieve your desired success? Let us help!

[Michael Stahnke]

On Fri, Feb 10, 2012 at 3:38 PM, Craig White <craig...@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 puppetd

That 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.