Issue #5547 has been updated by Banio Carpenter.
Seeing the same on server and clients running Debian squeeze
puppet: 2.6.2
Linux 2.6.35-24-virtual #42-Ubuntu SMP i686 GNU/Linux
ruby --version
ruby 1.8.7 (2010-08-16 patchlevel 302) [i486-linux]
I see this maybe about 25% of the time that I do a puppetd -t on the clients.
I just rerun puppetd -t and it usually works.
Usually it looks like this:
# puppetd -t
info: Retrieving plugin
err: Failed to prepare catalog: Could not run command from prerun_command:
Execution of '/etc/puppet/etckeeper-commit-pre' returned 1:
err: Could not retrieve catalog from remote server: Could not intern from pson:
source did not contain any PSON!
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
err: Could not run Puppet configuration client: Could not run command from
postrun_command: Execution of '/etc/puppet/etckeeper-commit-post' returned 1:
However, sometimes it pops up part way through a run of puppetd -t, but that is
rare.
For example:
root@domU-12-31-39-0A-98-E4:/home# puppetd -t
warning: peer certificate won't be verified in this SSL session
info: Caching certificate for client1.example.com
info: Retrieving plugin
info: Caching certificate_revocation_list for ca
notice: /File[/var/lib/puppet/lib/facter]/ensure: created
notice: /File[/var/lib/puppet/lib/puppet]/ensure: created
notice: /File[/var/lib/puppet/lib/puppet/parser]/ensure: created
notice: /File[/var/lib/puppet/lib/puppet/parser/functions]/ensure: defined
content as '{md5}d41d8cd98f00b204e9800998ecf8427e'
notice: /File[/var/lib/puppet/lib/puppet/provider]/ensure: created
notice: /File[/var/lib/puppet/lib/puppet/provider/httpauth]/ensure: created
notice: /File[/var/lib/puppet/lib/puppet/provider/httpauth/httpauth.rb]/ensure:
defined content as '{md5}b0f97c8929537caa76881bcaf161b820'
notice: /File[/var/lib/puppet/lib/puppet/type]/ensure: created
notice: /File[/var/lib/puppet/lib/puppet/type/httpauth.rb]/ensure: defined
content as '{md5}beab42ad1086202db040c72bc6783494'
info: Creating state file /var/lib/puppet/state/state.yaml
info: Loading downloaded plugin /var/lib/puppet/lib/puppet/parser/functions
info: Loading downloaded plugin /var/lib/puppet/lib/puppet/type/httpauth.rb
info: Loading downloaded plugin
/var/lib/puppet/lib/puppet/provider/httpauth/httpauth.rb
err: Failed to prepare catalog: Could not run command from prerun_command:
Execution of '/etc/puppet/etckeeper-commit-pre' returned 1:
err: Could not retrieve catalog from remote server: Could not intern from pson:
source did not contain any PSON!
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
err: Could not run Puppet configuration client: Could not run command from
postrun_command: Execution of '/etc/puppet/etckeeper-commit-post' returned 1:
If you need more info, just let me know.
----------------------------------------
Bug #5547: Periodic "source did not contain any PSON!" error on all clients.
Server / client version 2.6.2
https://projects.puppetlabs.com/issues/5547
Author: Alex Arwine
Status: Needs More Information
Priority: Normal
Assignee:
Category:
Target version:
Affected Puppet version:
Keywords:
Branch:
Puppetmaster running in daemon at version 2.6.2
Uses a custom external classifier
Clients all on 2.6.2
Every client will periodically come up with this error:
[1;35merr: Could not retrieve catalog from remote server: Could not intern
from pson: source did not contain any PSON! [0m
[0;36mnotice: Using cached catalog [0m
I spent some time trying to get a debug run where the error shows itself and
have attached the file (~56 lines)
My guess is it's something serverside, but I've been unable to track down the
problem or the solution in the irc.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
