similar to: handy tip against unhelpful "Could not intern from pson" error

I''ve been hitting this issue for a long time. well over a year and I guess it''s time to start pushing it to try to find the root cause. I''ve seen this reported several times in the past but I''ve never seen a resolution found for this exact problems. There are other root causes for pson errors that have been resolved, but not for the ones describing my

I''m running Puppet 2.7.1 on the master as well as the agent and just received a new error which doesn''t actually reference a module or a file, so I''m somewhat stuck as to how to debug this. Any pointers? The error is err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship target

I am getting this error on the clients. (I am running with --test). rerunning the command works as expected. This does not happen every time. I have no idea what the message means or more precisely what a PSON is... Russell -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

Hello! What does this error means? err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship target "Nagios_hostgroup[]" I cannot find it anywhere in my config... I have only 2 nagios_hostgroups, exported to server, then collected in nagios module. Any ideas? Cheers --- Grzegorz Marszałek

Hi i have the running i both sides, client and server sides the puppet 0.25.4 Get this error on server side: puppetmasterd[5363]: Report puppet_dashboard failed: wrong Content-Length format And receive this error on my client side: warning: Value of ''preferred_serialization_format'' (pson) is invalid for report, user default (b64_zlib_yaml) I am getting any reports on my

HI, i''m currently trying to connect a rails app using the "her" gem/library (since active ressource is gone since rails 4) to Puppet''s REST API. Now, "her" or activeressource both speak json, while Puppet speaks pson, which should be nearly the same according to some posts here. Communication already works but it seems that the response objects are not

Should I be concerned of the following error? - Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (b64_zlib_yaml) I''m running 0.25.4 on both server and clients and all are running Red Hat 5.4. Thanks, Clif -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this

Hi, I have a puppet infrastructure running 2.6.14 under Passenger with about 30 nodes. I''m just spinning up a new Cent 6.3, puppet 2.7.19 master. Right now I have the master built and configured using the same configuration as my 2.6.14 setup, with a few tweaks for the new version. Puppet on the master built itself fine. I have puppetd stopped on the master. I tried pointing one

*Hi guys!* * * *I''m trying to perform a service creation using SC and if this service is already created, using an "unless" we can avoid it. * *Sound very simple, but for any reason, when instructions are called by puppet they are not working instead you call directly, same instructions, using DOS, where works sweet.* * * *Here is part of the code:* $cmd =

Hi, I want to run Puppet on a Windows 2003 Server. I already have a working Puppetmaster (Scientific Linux). I installed Puppet on Windows like shown here: http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows This worked very well. But when I want to run puppet. puppet agent --test --debug I get the following output: (I already tried different ruby and puppet versions without

Hi there, I am used to traditional update-rc.d et all. Now I wonder how to add a a script that used to called by init.d (wit start/sop ..) to the new "service start xx" regime. All the tutorials I found talk about how to use update-rc.d.. thanks robert

Hello group, I am trying to run a puppet agent v3.2.2 against a puppet master with version 2.7.18, and I get this weird error: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Could not intern from pson: source ''"#<Puppet::Node:0x7f'' not in PSON! The run fails with "module not found", which is definitely there and

If I have something like this in my node file: daemontools_service::setup { ''carbon-cache'': service_name => ''carbon-cache'', .... extra_envs => { "GRAPHITE_STORAGE_DIR" => "/mnt/statsd-data/graphite-storage" "SOMETHING_ELSE" =>

Hello, I am running a puppet master version 2.7.5 on Centos 5.7 and a puppet agent version 2.7.5. I am simply trying to apply changes to files by defining a file resource in my manifest. When I execute my puppet agent to do the installation it complains it can not find the file meta data. Here is my manifest. class neospeech::config { file { "/usr/vwmrcpd/vwmrcpd/vwmrcpd":

Hi all, I''ve hit a curious bug in the Service.services method. This is in the pure Ruby version in CVS. Check it out and run this snippet: Service.services{ |s| p s.service_name p s.display_name } That will segfault after about 14 entries for me. It appears to be a problem with memcpy on line 658, but I couldn''t tell you why. The interesting thing is that the more I

is there a way to use the command: > > puppet master --compile <*nodename*> and have the output in PSON and not JSON? -- 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+unsubscribe@googlegroups.com. To post to this group, send

Hi, I''m rookie puppet user and I trying to establish simple Server-Client connection on configuration: Server: *Fedora F18*, Puppet 3.1.1 (installed by yum), Ruby 1.8.7 Client: *Debian 6.0.6*, Puppet 3.1.1 (installed by guide<http://shapeshed.com/setting-up-puppet-on-ubuntu-10-04/>), Ruby 1.8.7 Server sign client certificate with success but now I''m struggle with apply

Hi, Refresh doesn''t seem to be working with the launched service provider on OS X Lion (10.7.4). I''ve come up with a simple "service" script, plist file and puppet script to apply to demonstrate. The problem. Here''s the shell script which logs an initial starting message and then just loops logging a "Still running…" message.

Good morning , I could help to debug this problem ? "puppet agent - test" Debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using pson Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class pentaho for s <http://srvdev206.cia.stefanini.com/> erver.test.com /usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:185:in

Hi all, If you take a look at the service.rb file in the win32-service repository (the new one in the toplevel repository path), I''ve got this bit of code, which succeeds, but I can''t seem to unpack the data structure properly. Did I pack it wrong to begin with? I should know this but I''m spacing out. proc_status =