I have the same problem. Looking at the puppet logs on the affected nodes it looks like the puppet agent will occasionally assume "localhost" as its fqdm and then gives up when the certs don't match. Maybe it's connected to waking from sleep and the puppet agent going off before all relevant networky things have been established. I too would be majorly chuffed with some kind of fix.
Phil On Wednesday, February 12, 2014 1:24:27 PM UTC+1, Kristian Johannessen wrote: > > I have a strange problem with some of my puppet clients. After a while > they stop reporting in with the master. If i run the puppet agent manually > with command (sudo puppet agent -t) everthings looks fine. > > The puppet agent is started at boot by the launch daemon that is described > at puppetlabs.com. I have checked that it's running in the background. So > it seems to me that there is a issue with the puppet schedule. The issue is > not relatet to OS, because i have multiple clients running both 10.8 and > 10.9 that's working... > > If anyone have any suggestions how to fix this i would be thrilled.. > > Cheers, > Kristian > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5db0b07e-01c3-406a-bf1e-e6d57502fa08%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
