Sorry Jed I didn't realise that you didn't know about .puppet directories. A .puppet directory is created in your home directory if you accidentally run puppet as yourself and not as root. The problem that I had was that sometimes puppetd was correctly reading SSL settings from /var/lib/puppet/ssl and sometimes from ~/.puppet/ssl (I started puppet sudo'ed from my account).
But I don't think that this is Douglas' problem as he is only getting his error occasionally whereas mine was happening once every three or four runs at the beginning and then increased in frequency. But still my experience might help a bit as I found that, at least in my case, no PSON meant actually meant no content at all was fetched from the puppetmaster. And the place to look to see if that is the case is the web server log on the master (in /var/log/puppet or whatever). I hope that this helps. On Mar 4, 4:55 am, Jed <jedbl...@gmail.com> wrote: > Hi doug, I've been getting this as well , someone suggested searching > the entire filesystem on the client for a directory called .puppet and > delete any found. I haven't tried this yet though > > On Mar 3, 2:36 pm, Douglas Garstang <doug.garst...@gmail.com> wrote: > > > > > I'm sure it must already be a known bug, but I've been getting this message > > frequently on the clients: > > > Could not retrieve catalog from remote server: Could not intern from pson: > > source did not contain any PSON! > > > Happens erratically but it's frequency seems to have increased with my > > upgrade from 2.6.3 to 2.6.4. Getting rather sick of it because I have to > > restart the client multiple times to get it to stop. > > > Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
