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!
On Monday, 3 March 2014 15:27:15 UTC, Philip Powell wrote:
>
> Hey Moses
>
> I'm still experiencing the same problem
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
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
On Friday
Phil, Kristian,
Would you mind posting a gist (any private info retracted of course)
of the logs you find this information in?
On Thu, Feb 13, 2014 at 5:44 AM, Philip Powell wrote:
> I have the same problem.
> Looking at the puppet logs on the affected nodes it looks like the puppet
> agent will
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 ne
