similar to: puppetd stops

Anyone know what this is? It doesn''t seem related to puppet but I''m stumped. info: Loading facts in dmidecode info: Loading facts in cpuinfo debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml; using pson /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/rest.rb:55:in `deserialize'' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/rest.rb:69:in

I have this: class foo::foobar ($version) { } which is called like this: class facility::sanjose inherits facility::common { class { foo::foobar: version => "1.3.13" } } puppet complains with this on the client: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find parent resource type ''facility::sanjose'' of type hostclass in

Hello Everybody, I am trying to install the puppetdb on the same machine as am running my puppetmaster. I am getting the following error when am trying to connect the agent: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit ''replace facts'' command for ftldwshost180.wsdev.citrix.com to PuppetDB at

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, 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 everyone, I have a puppet master/client infrastructure setup with apache. When on the same datacenter I don''t have any problem. I am trying to use another datacenter, so I setup the fileserver.conf as followed: # Files in the /path/to/files directory will be served # at puppet:///mount_point/. [modules] allow *.datacenter1 allow *.datacenter2 [plugins]

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

Greetings. I am trying to set up a test puppet server in my environment to evaluate windows clients. On the server side, I am using puppet 2.7.14 (from the repos). I''m using the 2.7.14 windows 64 bit on the client (windows 2008 R2). I have another puppetmaster already using "puppet" hostname in DNS (running a very old version of puppet - can''t upgrade yet for various

Hi, I''m serving the puppetmaster application with its config.ru through unicorn - proxied by nginx. I''m using unix sockets, 4 workers, and 2048 backlog. The clients - after their typical "puppet run" - send back a report to the master in YAML. Some clients whose reports tend to be large (close to 2mb) get a 502 bad gateway error and error out. nginx log: 2010/10/22

I''m rather new to puppet and I''ve been trying to get a module to work on the client servers. Right now I''m trying to get http://forge.puppetlabs.com/ghoneycutt/pam to run. When I try to run it I get these two errors: err: //pam/File[/etc/pam.d/sshd]: Failed to retrieve current state of resource: Could not retrieve information from source(s)

Hi guys, I have a box that needs to identify itself to the puppetmaster as something different from the FQDN. I added certname to the agent configuration before the first run, but it doesn''t seem to be sufficient. The certificate was generated for the FQDN, and the host appears in the dashboard as the FQDN, and the node name used to evaluate the manifest is also the FQDN. I would

We are seeing this error in our log files on some clients: puppetd[15068]: Could not run Puppet configuration client: undefined method `initvars'' for #<Puppet::Type::Package:0x2aaaabbb4858> Where do I begin troubleshooting this? The client software versions are: ruby-1.8.5-5.el5_4.8.x86_64 ruby-libs-1.8.5-5.el5_4.8.x86_64 ruby-shadow-1.4.1-7.el5.x86_64 facter-1.5.8-1.el5.noarch

Hello, all. I am getting the following error on a couple of my puppet nodes when I run puppetd -v -o --no-daemonize --no-splay: err: Could not retrieve catalog: undefined method `-'' for #<XMLRPC::DateTime:0xb7c729e8> The error goes away if I add --ignorecache, but I''m not sure that''s quite the fix I''m hoping for. It will also go away if i remove my

Hi again, puppetd started to hang with 100% CPU usage all of the sudden. Strace just keeps repeating these 2 lines: --- SIGVTALRM (Virtual timer expired) @ 0 (0) --- sigreturn() = ? (mask now []) In logs it hangs with this message: debug: Calling fileserver.describe But lots of these fileserver.describe calls prior to hang are successful. If I run it with puppetd

Hi, I''m testing puppet from the subversion trunk. I have a rather hacked-together system to install a CRM into one of my nodes, which worked (more or less) with version 0.19.3. When I tried to do a puppet run on a completely clean node it seemed to stall on the ''compilation'' part (I do an exec of ''perl Makefile.PL'' in the appropriate dir). When I broke

Hi, My puppet master don''t want to start anymore. Any idea ? [root@puppetmaster requests]# puppet master --no-daemonize --debug debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist debug:

After upgrading my puppetmaster server to 0.22.2 using David''s src RPM''s for RHEL4 rebuilt for x86_64 i am getting the following error when puppetd attempts a configuration run. Mon Mar 26 10:05:43 EST 2007 Puppet (err): Could not run Puppet::[1]Network::Client::Master: Invalid value ''nil'' for noop When puppetd is started the initial run is

I see in the changelog that: You now must specify an environment and you are required to specify the valid environments for your site. (#911) Does this mean that the puppetmaster has to be updated before clients work correctly? I ask because I''m testing out a client upgrade to 0.24.0 (server is still 0.23.2) and this is what I''m seeing: [~]% sudo /foo/bin/puppetd

Hello, we have one puppet server managing approx servers, all FreeBSD. The problem is that the puppet clients all hangs, one by one, eventually. They will run for anything between an hour up to a week. But eventually the all hang. We really like puppet and want to keep using it. But the way it is now is completely unusable. We''ve tried many versions, from 24.x, and now 2.6.1rc1. But

I updated to 0.22.3-1 from the dlutter repo (CentOS 4.4) and I''m still having trouble adding new nodes as others saw from the previous version, though I believe the error is different now. The procedure I used was: <client> /etc/init.d/puppet once -v <server> /usr/sbin/puppetca --sign nodename <client> /etc/init.d/puppet once -v This used to work for new nodes, now I