Yep, it's not finding the pidfile because the init script is looking in
/var/run/puppet/agent.pid and the daemon is putting it at
/var/lib/puppet/run/agent.pid. So for now I'm going to modify the init
script wherever we are having this problem.
We're upgrading the systems as we update them to Centos7.
I don't know what it is about the environment that's different. That'll be
an investigation for another day. The change to cron was basically to
spread out our agent communication load throughout the hour (we were only
having them check in hourly -- for us, that's plenty). This started as a
way to figure out if there was somehow something different in the
environments. I think there is. Just need to figure out what it is now.
Thanks!
On Monday, August 8, 2016 at 8:40:24 AM UTC-4, Bret Wortman wrote:
>
> We've been using cron to manage our puppet agents for the past few years
> but have discovered some issues where it's running under a different
> environment and is having trouble completing when run in cron, but it works
> fine as a daemon or from the command line. So I'm preparing to switch over.
>
> Unfortunately, the following doesn't work for my 3.8.6 agents on Centos 6
> systems even though it works fine for 4.3 agents:
>
> service { "puppet":
> ensure => running,
> enable => true,
> hasstatus => true,
> hasrestart => true,
> }
>
>
> What we see on some agents is that puppet will restart the service each
> and every time it runs, which gives us lots of false "changes".
>
> # service puppet status
> puppet dead but pid file exists
> # ps aux | grep puppet | grep agent
> root 9879 0.0 0.0 134404 43516 ? Ss 12:22 0:00
> /usr/bin/ruby/usr/bin/puppet agent
>
>
> Has anyone else seen this or know of a workaround? I've tried various ways
> of providing a "status => " command but haven't found anything that works
> yet.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/4affc1bf-5721-4883-822f-61e9e007c162%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
