similar to: Puppet daemon performance problems

Hi, I have Redhat 9 & RHEL 4.2 with puppet clients installed. When is use puppetd -test the updates get effected, but when when running them as daemon mode nothing happens. ## Nothing Happens - no change is detected /etc/init.d/puppet status puppetd (pid 15538) is running... ## When running manually puppetd -test the changes from server gets updated. Is there any

Hello, I tried to compile and install R. After I ran make 2>&1 | tee log ., I got the following error: making system.d from system.c system.c:37: readline/readline.h: No such file or directory make[3]: *** [system.d] Error 1 make[3]: Leaving directory `/afs/lsa.umich.edu/group/admin/software/build/R/R-1. 0.0/src/unix' make[2]: *** [R] Error 2 make[2]: Leaving directory

Hi, I have a lot of systems where the puppetd doesn''t do anything .. When I test with puppetd -tv, it s running well, but when it is started as deamon th process do nothing :( How can I debug this ? Vincent May 29 10:07:56 puppetd[6160]: Reopening log files May 29 10:07:56 puppetd[6160]: Starting Puppet client version 0.24.8 May 29 10:07:56 puppet: puppetd startup succeeded May 29

(I''m emailing the list, rather than direct.) Adnet Ghislain wrote: > Hello, > > More on my deployment, i have an issue where the fact sometime does > not load and it seems that they do not work and as i rely on facts in it > ll fails: > > Oct 6 02:54:18 oiseadmin puppetd[42243]: Could not call > fileserver.list: #<Errno::ECONNRESET: Connection reset

I just upgraded from 0.23.2-1 on RHEL 4&5 to 0.24.1-1. I used Dlutter''s repository. What a mess I''m in now. Anyway to make a long story short I moved all of the old configs out of the way (/etc/puppet, /var/lib/puppet) and started over with a fresh install. I can''t get puppetd on the server to request a cert. If I do a "puppetd -v --waitforcert 90" the

Hello all, I have puppet rpm on internal repository for updating it to servers that don''t have it on their normal repos (Centos, Fedora Core 4 or older...) Then I have this to ensure that puppet is at latest version: package { "puppet": ensure => latest, provider => yum, } I added puppet 0.22.3 to my internal repository and all servers updated to that version,

On Nov 2, 2023, at 4:39 PM, Grant Erickson <gerickson at nuovations.com> wrote: > On Nov 2, 2023, at 4:32 PM, Damien Miller <djm at mindrot.org> wrote: >> On Mon, 30 Oct 2023, Grant Erickson wrote: >> >>> I have an NXP i.MX6-based armv7l-dey-linux-gnueabihf system in which I >>> am seeing some as-yet-unaccountable behavior in sshd when compiled with

I found what the problem is but I am posting this so hopefully people don''t scratch their heads when this happens. I need to be able to configure different things depending whether I''m running on a system that has a Xen kernel or not. I added a fact in /var/lib/puppet/facts/ Facter.add("xen_kernel") do server= `uname -r` if

Hello all, puppet hangs while trying to restart a daemon when the associated config file changes, here the log: Mar 19 11:30:04 ingentTest puppetd[27390]: Starting Puppet client version 0.22.0 puppetd[27390]: Starting configuration run puppetd[27390]: (/ingenttest/qualsevolnode/guaita[guaita]/File[/etc/guaita.conf]/content) synced puppetd[27390]:

I''ve built a puppet solaris - package which is distributed via jumpstart at installation time of a solaris 10 machine. It''s postinstallation registers the puppetd into smf and starts puppetd afterwards. Puppetd connects to puppetmasterd, gets ist certificate signed (autosig on) and the configuration stuff. Now the interesting part: a new solaris zone is installed via puppet.

I want to use puppetrun so I added --listen to the puppetd command-line. Puppetd would run and then immediately exit. I couldn''t figure out the cause because there was nothing in the logs. I finally figured it out when I ran it with --verbose. # puppetd --listen --verbose Will not start without authorization file /etc/puppet/namespaceauth.conf My guess is that the fatal message is

Hey every one, Over the past week I have been exploring puppet and had been ignoring an oddity in its output that Luke helped me figure out today. It all started with trying to configure puppet to configure iptables using redhats utility system-config-securitylevel-tui on rhel4. I was able to get it up and running using the following configuration: node default{ firewall {rhel4:

> I''ve built a puppet solaris - package which is distributed via jumpstart > at installation time of a solaris 10 machine. > It''s postinstallation registers the puppetd into smf and starts puppetd > afterwards. Puppetd connects to puppetmasterd, gets ist certificate signed > (autosig on) and the configuration stuff. > Now the interesting part: a new solaris zone

What is puppet doing here? Nov 17 00:02:01 gumby yum: Installed: tf-starterkit-tfel0-1.0-1.tf.noarch Nov 17 00:02:01 gumby puppetd[720]: (//Node[gumby.fr.xxx.com]/Starterkit::Setup[tfel0]/Package[tf-starterkit-tfel0]/ensure) created Nov 17 00:02:07 gumby yum: Installed: tf-jboss-server-4.2.3.GA-1.tf.noarch Nov 17 00:02:07 gumby puppetd[720]:

Hello, I have got the following error while starting the puppet client, please find the following ===================== root@epsilon [/usr/src]# /etc/init.d/puppet start Starting puppet: /usr/sbin/puppetd:159:in `require'': no such file to load -- puppet/application/puppetd (LoadError) from /usr/sbin/puppetd:159 ===================== I have checked ruby installation and it seems to be

On Apr 30, 2007, at 4:44 AM, Frank.Munsche@izb.de wrote: > I''ve built a puppet solaris - package which is distributed via > jumpstart at installation time of a solaris 10 machine. > It''s postinstallation registers the puppetd into smf and starts > puppetd afterwards. Puppetd connects to puppetmasterd, gets ist > certificate signed (autosig on) and the

Trying to get an EC2 AMI running puppet 0.25 and i''m hitting a problem. After installing the rpms and starting puppet it was just quitting with only: puppetd[3313]: Reopening log files In the log file. When running it with the following I get some more output. -bash-3.1# puppetd -D -d -t --trace debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug:

Hello, I''m seeing the following when I run puppetd --version /usr/sbin/puppetd:157:in `require'': no such file to load -- puppet (LoadError) from /usr/sbin/puppetd:157 I thought upgrading ruby to 1.8.5 would solve the issue but it has not. In any case, here are the relevant rpm versions... ruby-1.8.5-1.el4.centos ruby-rdoc-1.8.5-1.el4.centos

This is causing me to --clean the first key, and --sign again after the second run of puppetd --test First Run: [root@asmc1n2 ~]# puppetd --test warning: peer certificate won''t be verified in this SSL session. info: Creating a new certificate request for asmc1n2.dev.gridapp.com info: Creating a new SSL key at /var/lib/puppet/ssl/private_keys/asmc1n2.dev.gridapp.com.pem ... Second

I''m just starting a roll out of Puppet and I''m seeing a problem on maybe 25% of client nodes. The symptoms are that the clients stop updating. In the Puppetmaster log, I''m seeing things like: Feb 9 20:10:23 vs4 puppetmasterd[17942]: Compiled catalog for xxxx in 0.05 seconds Feb 9 20:40:41 vs4 puppetmasterd[17942]: Compiled catalog for xxxx in 0.05 seconds Feb 9