Recently I rigged up a script to email me a list of agents that did not
send any reports to puppet server in last 24 hours. Each night it lists
about a dozen agents, mostly but not always the same ones.
They share a common pattern:
Agent is running in deamon mode but makes no updates.
Each time the agent kicks a run the only impact is to write the following
to /var/lib/puppet/state/last_run_summary.yaml:
---
time:
last_run: 1327963581
/var/lib/puppet/state/puppetdlock gets created and removed as normal.
No other file in /var/lib/puppet gets touched.
No messages get logged in either client or server.
Not report gets sent to server.
Restarting puppet agent or rebooting the node does not fix the problem.
Running puppet agent -t works fine.
Most agents in our site do not show this problem. I have confirmed all
agents are running the same versions of puppet, ruby and linux kernel:
Distro is SLES11-SP1-x86_64
2.6.32.46-0.3-default
puppet-2.7.9-11.1
ruby-1.8.7.p72-5.30.5
facter-1.5.8-3.1
Starting puppet agent with debug flag shows no additional info, since
nothing gets logged at all. but I am sure there are other options/tricks
I don''t know.
--
-ashley
Did you try poking at it with a stick?
--
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.