similar to: puppet performance and inability to retrieve file metadata

Hi all, The last 2 weeks we have been having problems with puppetd just randomly stopping. The only thing the log shows is: <snip> Apr 21 12:14:59 relay puppetd[1376]: Finished catalog run in 4.78 seconds Apr 21 12:30:07 relay puppetd[1376]: Finished catalog run in 4.76 seconds Apr 21 12:45:20 relay puppetd[1376]: Finished catalog run in 4.61 seconds </snip> There is no pattern when

Hey Folks, I''m looking at doing automated provisioning of new servers and am trying to integrate puppet into this process. What I''m wondering though is what the best process for securely registering a new node is. At the moment the first time puppet is run I have to then accept the certificate on the puppetmaster and then run puppet again. What I would like to do is accept the

Hey list, I'm wondering if there is any advantage to be gained by using kerberos with pam_winbind. I've configured pam_winbind and enabled krb5_auth though apart from being granted a ticket, I'm unsure as to any advantage that would be gained by enabling Kerberos. Thanks, Matt Delves -- --------------------------------------------- Matthew Delves System Administrator Information

Hi I''m getting this error with a 0.25.1 puppetmaster and 0.25.1 node. Nov 4 14:43:35 devcentos5 puppetd[26099]: (//network-config::base/File [hosts]) Failed to retrieve current state of resource: Error 400 on SERVER: Not authorized to call find on /file_metadata/network-config/ hosts/hosts.devcentos5 Could not retrieve file metadata for puppet:///network-config/hosts/hosts.devcentos5:

Hi, I just upgrade to the next version of puppet (0.25.1-2) and now passenger broke (puppetmaster is still working). I have followed the guide on http://github.com/reductivelabs/puppet/tree/master/ext/rack but still I get a errorcode 500 with the error: support:~# puppetd --test --debug debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug:

I''m troubled with a node-definition not able to resolve a class: Could not find class rhnsd::common at /etc/puppet/manifests/nodes.pp: 8 on node X Content of manifest/site.pp: import "nodes.pp" [...] The layout of modules/rhnsd/ is: |-- files | `-- up2date-rhn |-- manifests | |-- client.pp | |-- common.pp | |-- init.pp | `-- rhn.pp A `cat'' from each

Hi all. I am testing 0.25.4 to upgrade from 0.23.2. In testing, I found two strange messages on 0.25.4 which I have never found on 0.24.3. So could you tell me what these messages mean and how to fix them. [Environment] Puppetmasterd -version : 0.25.4 -OS : Solaris10 10/09 Puppetd -version : same as Puppetmasterd -OS : same as Puppetmasterd [Strange messages] 1.When Puppetd

I''ve been hacking at puppet for the past week or two, and came up with some great stuff, but I''m wondering if there''s a way to tie it all together To create a virtual machine for our company''s QA environment, I''m currently doing 3 things: #create a vm node vmsvr2 inherits default { include vmserver vmserver::vm {

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

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

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, 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

I have a puppet master on Centos 6.3 connected and working properly with other Centos 6.3 agent. I installed puppet agent via gems on a RED HAT 4 node. This is what happens when I try to sign certificate for the new node: AGENT [root@FP2 ~]$ puppet agent -t Info: Creating a new SSL key for fp2 Info: Caching certificate for ca Info: Creating a new SSL certificate request for fp2 Info:

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

Hey All, This is probably a gotcha of some kind. That is to say I''ve missed a configuration somewhere. I''ve recently moved over to using mongrel as the puppet server type and having nginx proxy to one of four mongrel instances. What I''m seeing though is that when I try to run a new node (one that has been created post moving to mongrel/nginx) is that it returns with the

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

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

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