On 16/09/14 20:00, Trevor Vaughan wrote:
I had a problem similar to this when an error was introduced to my puppet master's served code base.

To troubleshoot I did the following:

1) Restart the puppetmaster process (passenger, whatever you're using)
2) Remove everything under /var/lib/puppet/lib/facter/* on the clients that are having the issue.
3) Re-run the puppet agent on the affected node

One of two things should happen, either your facts will be re-sync'd and everything will be fine or an error will be thrown noting that you have an error somewhere else.

If this *doesn't* happen, check the server logs and see if there's something more insidious happening.

Good luck,

Trevor

Thanks for your advice. I'll try this when I'm back at work in the morning. For now, allow me to leave you with this video, which seems to summarise your advice ;)

https://www.youtube.com/watch?v=kb2gzteVNa4

Cheers,
Jonathan

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/541896E8.3090003%40bristol.ac.uk.
For more options, visit https://groups.google.com/d/optout.

Reply via email to