similar to: puppet agent / master version compatibility?

on my puppet master server (v 2.7.17 , both server and client version) , the puppet agent can''t connect to itself. other clients connected to this puppet server are working fine. the hostname is puppet.domain.com [root@puppet /]# cat /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is ''$vardir/log''. logdir = /var/log/puppet

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

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 group, I am managing an NFS mount with puppet. And it does not work, and seriously I really don''t see how this can work out nicely. First I make sure with a file {} class that the directory I want to mount exists. Cause it is used by the webserver it should belong to the wwwrun/www group on the system. No prob. Then I mount the NFS share on the dir. No prob. On the 2nd run of

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":

Hoping you guys might be able to help me out, I''m not sure what''s wrong but puppet agent hangs for over a minute, no resource spikes (CPU, memory, etc all stay basically the same as without starting puppet, barely a blip, and I''ve got more than enough headroom). It''s not a serious issue for continuous usage, but really, really annoying when testing the manifests

Not sure if people are already aware of this, but it might save someone some time in the future. I''ve been tracking down the following error today, it''s rather unhelpful in telling you where the problem is in your manifests: # puppetd --test info: Retrieving plugin err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could

Hello, I''m having some trouble. I keep getting the following warnings when trying to run: $ puppet master --no-daemonize /usr/local/build/puppet-bundle/vendor/gems/ruby/1.9.1/gems/ puppet-2.7.12/lib/puppet/external/pson/pure.rb:7:in `<module:PSON>'': iconv will be deprecated in the future, use String#encode instead. Could not load confine test

Hi group, I am trying to template a bash script with puppet. Unfortunately, this fails with a bang, and even more unfortunately I have no idea why. The script starts with the usual #!/bin/bash When I run puppet, I get this: info: Caching catalog for l1211022.sdst.sbaintern.de err: Failed to apply catalog: Parameter source failed: Could not understand source #!/bin/bash [... complete

OK. What did I booger up this time ? agent.myexample.org and puppetmaster.myexample.org are the same server. ---------------------------------------------------------------------------- # puppetd --no-daemonize --onetime --debug --noop debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not

I am new to using puppet and having trouble when updating an agent from a master which has a lot of files. Usually the updates work, but when there are a lot of files I get this error when running: sudo puppetd --test --server puppet.example.local --trace --debug >>> debug: Failed to load library ''rubygems'' for feature ''rubygems'' debug: Failed to load

Hello readers, I have this little issue that my puppet client refuses to do anything because of SSL validation errors. Maybe I''ll just post dump of what happens, that makes it clear I hope. Does anyone have a suggestion why that might happen? what I already checked: On the master: - Puppet and puppetmaster is running - Something is listening on Port 8140 (although I cannot

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

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

Hi, i''m a newbie about Puppet( 1 month ~) i got error on generate temp file, i''ll explain my situation: -i have a puppetmaster(version: 3.3.0),executed on root and a puppet agent(version 2.7) provisioning by vagrant,executed on root -my site.pp, where webserv is a parametrized class, and typews is a parameter to choice nginx or lamp module, -i have my Enc node with path

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

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

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

Hello, Running into a problem when wanting to daemon-ize the agent. It doesnt seems to do anything: - cannot find any daemon process with (ps aux | grep puppet) - the config is not updated after editing some params on the master - /var/log/puppet stay empty... while, when logged as root, it is working without issue with $puppet agent --test. ##Conf Ubuntu 12.04 Puppet 2.7.11 ## Daemon is

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