Some of my OS X clients stop checking in with puppet master.

[Kristian Johannessen]

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

[Philip Powell]

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

[Moses Mendoza]

Phil, Kristian,

Would you mind posting a gist (any private info retracted of course)
of the logs you find this information in?

> --
> 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...@googlegroups.com.
> 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.



--
Moses Mendoza
Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco -
http://bit.ly/pupconf14

[Philip Powell]

Here's one. (When it's in this state I can ssh in and do a sudo puppet agent -t and everything's fine again.)

https://gist.github.com/pkpowell/9011179

Somewhat surprisingly there was no private info there to redact. Would there be more relevant info in the system.log?

Cheers

Phil

[Philip Powell]

Hey Moses

I'm still experiencing the same problems with puppet checking in as 'localhost' after waking form sleep. Any ideas what could be causing this?

The clients are either running vers. 3.4.2 or 3.4.3.

Any other troubleshooting suggestions?

Cheers

Phil


On Friday, February 14, 2014 7:36:44 PM UTC+1, Moses Mendoza wrote:

[Merlin Hartley]

We had this problem before and the only way we have found to fix it is to specify the certname in the each client's puppet.conf
THe problem then just goes away .

Hope this helps!