similar to: warning: fork terminates thread

I''m getting the following error on the client: /usr/lib64/site_ruby/1.8/puppet/util.rb:300: warning: fork terminates thread at /usr/lib64/site_ruby/1.8/puppet/external/event-loop/event-loop.rb :123 when using the following code: case $operatingsystem { CentOS: { service { "nrpe": ensure => true, enable => true,

Hi working with the following puppet-0.24.1-1 puppet-server-0.24.1-1 ruby-1.8.1-7.EL3.8 rhel3 u8 The puppetmaster is running on rhel4 u5 I am working with puppet and rhel3 u8 and I have any an issue anytime I ask puppet to interact with yum for the record - yum from the cli works perfectly I setup a class to manage ntpd and in the class I have the following function # make sure ntpd is

Hi I''m having the following problem and tried already several workarounds, as well benp- tried to help me on irc. I copied the ntp modul from DavidS repo and adapted it in the Service part to run as well under openbsd. Which was just adding some binary if openbsd is the operatingsystem. However then I wanted to run it as well on a gentoo system (on centos, debian and openbsd it was

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

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

This is particularly nasty, since it''s on the puppetmaster itself: [root@puppet tmp]# rpm -q yum puppet puppet-server yum-3.0.5-1.el5.centos.5 puppet-0.24.0-2.el5 puppet-server-0.24.0-2.el5 [root@puppet tmp]# cat /etc/issue CentOS release 5 (Final) Here''s the output of puppetd --debug: notice: Starting catalog run debug: Loaded state in 0.01 seconds debug: Prefetching rpm

Hi, I just got my local yum repo setup so that I can use puppet to install packages... and it looks like something is not working. <snip> Tue Sep 19 02:13:05 PDT 2006 Puppet (notice): Starting configuration run Tue Sep 19 02:13:10 PDT 2006 //default/java/package=jdk/ensure (err): change from absent to latest failed: Could not update: Could not execute ''/usr/bin/yum -y install

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

On 5/24/2015 12:22 PM, Gordon Messmer wrote: > On 05/24/2015 11:41 AM, Kirk Bocek wrote: >> to activate your selected daemon. I just used the new systemd commands, >> thinking that would be enough. So I tried that and rebooted. Nope, same >> problem: > > chronyd and ntpd both use UDP port 123, so each will terminate the > other when it starts. If both are enabled,

Hi, I have a couple of FreeBSD-servers that I try to manage using puppet. I''m just trying it out at the moment and have just deployed 5 new boxes (from PXE and scripted installation so supposedly they are all identical except for the name and ip-addresses). On two of the servers I get the error-messages at the bottom of the post. The first error- message I get every time I run puppet on

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You folks were so helpful with my last problem I thought I''d try again. I''m attempting to use the services filetype to ensure that ntpd is running on all my hosts. Unfortunately this does not seem to be working on my Gentoo test system. I get the following output on the client log: puppetd[3436]: Starting configuration run

On 5/23/2015 11:22 PM, Luigi Rosa wrote: > Kirk Bocek wrote on 24/05/2015 04:37: >> So I've built my first CentOS 7 host and am learning all the new ways >> of doing >> things. I setup and enabled ntpd but after a reboot I get: > > In CentOS 7 is bettere to use chrony, here's an howto > > http://linoxide.com/linux-command/chrony-time-sync/ > So

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

Ok, I installed Ruby/LDAP to try and get Puppet''s ldapnodes support working and despite doing this I am still getting errors from puppetmasterd "notice: Could not set up LDAP Connection: Missing ruby/ldap libraries" followed by "info: Skipping ldap source; no ldap connection". I traced down this particular message to: lib/puppet/parser/interpreter.rb and it appears

this time when I try to connect the first node: [root@qaagt20 ~]# /etc/init.d/puppet start Starting puppet: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': No route to host - connect(2) (Errno::EHOSTUNREACH) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'' from

I don''t know what it is with puppet''s certificates, but once again, they are behaving strangely. Client is reporting: debug: Using cached certificate for auth01.fre.livegamer.com /usr/lib/ruby/site_ruby/1.8/puppet/ssl/host.rb:166:in `certificate'' /usr/lib/ruby/site_ruby/1.8/puppet/ssl/host.rb:227:in `wait_for_cert''

Hi. When running "puppetd --server <puppetmaster> --waitforcert 50 --test" on a puppet client we get the following error: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': getaddrinfo: Name or service not known (SocketError) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect''

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:

I''m attempting to deploy puppet via an NFS share. It''s on a local-only network, and it will contain only ruby (gems) and whatever is needed. Seems simple enough, but tonight I am having an issue with this error: # service puppet start Starting puppet: /local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:36:in `gem_original_require'': no such file to load -- openssl

Hi Luke and other people working on 0.24. I hope this is constructive. So, I have our configuration working against a checkout from git as of last night. Subject to (sorry, here''s the big but :) * external_nodes script is not being called (#951) * Custom types aren''t working unless I drop them into $rubysitedir/puppet/{type,provider}. Previously they worked in