Issue #5811 has been updated by Nigel Kersten.
So even after reboots the client isn't contacting the server for a fresh catalog? If that's the case, can we get a full --debug --trace --evaltrace log from such a client? It's a little difficult to work out where the problem is from here. ---------------------------------------- Bug #5811: Puppetd doesn't re-attempt connections after puppetmaster failure https://projects.puppetlabs.com/issues/5811 Author: eric sorenson Status: Needs Decision Priority: Normal Assignee: Nigel Kersten Category: agent Target version: Affected Puppet version: 0.25.5 Keywords: Branch: After a particularly evil failure that took out all of my production puppetmasters earlier this week, some long running puppetd clients are still using their pre-crash catalogs. Mac OS X 10.5.5, Ruby 1.8.7-266, Puppetd 0.25.5. e.g. <pre> [root@wibble003 /var/puppet]# ls -l client_yaml/catalog/ total 7128 -rw-r----- 1 root wheel 175068 Jan 7 13:33 localhost.yaml -rw-r----- 1 root wheel 3471871 Jan 4 15:43 wibble003.foo.com.yaml </pre> Puppetd wakes up according to the schedule but even a USR1 does not cause it to contact the server. Oddly the host has been rebooted since the outage so this puppetd is the original PID from system boot but the catalog is from *before* the reboot. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
