Well my thinking was that since the certificate is stored in the home directory, messing with the home directory somehow changed the masters certificate, which is why none of the agent's keys match it. I really don't know though, I'm kinda new to puppet and linux. In any case, I can't clean the agent certificates from the master since I can't run the command to do so, unless there's a way to do it manually.
On Monday, May 5, 2014 10:22:44 AM UTC-4, Felix.Frank wrote: > > Okay, thanks. > > I don't really see how messing up permissions on the master would cause > such behavior. > > Generally, the error means that your agent has lost its private key, > generated a new one, yet the master still retains a certificate it has > signed for use with an older private (agent) key. > > To fix this, you would actually need to clean each last *agent* > certificate from the master, then sign new ones. Although why it would > suggest to clean the master's certificate is beyond me. > > HTH, > Felix > > On 05/05/2014 04:18 PM, Dan Pasacrita wrote: > > Hey, sorry, I kinda posted this in a hurry since I've been taking a ton > > of calls during, sorry about that. This error is occurring with every > > single agent apparently, including the agent on the master machine. > -- 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/c90cb0a0-e16d-4844-b54a-7070371712d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
