similar to: puppet on RHEL4

I have created my first ''fact'', first attempt at Ruby too, and configured the fileserver to server it but when a Fedora (5 or 6) client sync''s puppetd appears to hang. CentOS clients sync and use the new fact fine. Find attached the fact file and the output from ''puppetd --debug --factsync'' on a FC5 client is below. This is a 0.20.1 client and

Using RPMs for el4 (0.22.3). Been trying to get templates to work, but have found problems. I created a very small template, and this works well, variables substitute, great. I tried a much larger one (an httpd.conf), and puppetmaster crashed. the remote puppetd first reported an SSL certificate problem, then on seconds run, "cannot connect to server." Hacked the template down to

So I have been trying to run puppet once in my kickstart %post scripts but every time it detaches and daemonizes even though I have explicitly stated otherwise. Am I missing something? # rpm -q puppet puppet-0.24.8-1 # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug debug: Creating default schedules debug: Failed to load library ''shadow'' for feature

Just wondering if anyone has built (or found) Puppet rpm packages for RHEL4 x86_64 version. James ********************************************************************************* Important Note This email (including any attachments) contains information which is confidential and may be subject to legal privilege. If you are not the intended recipient you must not use, distribute or copy this

Hi all, We are still running a few dozens of RHEL4 within our Datacenter and I''d like to install a puppet agent to at least collect some inventory (facter) and do a little bit of configuration management. The only puppet agent I managed to found for el4 is 0.22.4 (quite old) which we installed with a facter 1.6.4 and a ruby 1.8.7.72. At first we had issues with "requires"

Hi, I just want to install dovecot 1.0 beta7 from atrpm and noted that it depends on a non official dependency. If you have RHEL4 (Centos) 4.3 fully updated and you try to install: http://dl.atrpms.net/all/dovecot-1.0-0_10.99.beta7.el4.at.i386.rpm You get this error: # rpm -ivh dovecot-1.0-0_10.99.beta7.el4.at.i386.rpm error: Failed dependencies: openssl >= 0.9.7f-4 is needed by

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,

---> Package libevent.i386 0:1.1b-1.el4.rf set to be updated --> Running transaction check --> Processing Dependency: libevent-1.1a.so.1 for package: tor --> Finished Dependency Resolution Error: Missing Dependency: libevent-1.1a.so.1 is needed by package tor

Here is the output from yum -y upgrade without the error parts... Its odd because it updated all of these first time round. I have dared reboot the box yet, for fear it won't come back up... Setting up Upgrade Process Setting up Repos Reading repository metadata in from local files Resolving Dependencies --> Populating transaction set with selected packages. Please wait. --->

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

Hello All, I''m using the "Branch Testing" approach documented at https://reductivelabs.com/trac/puppet/wiki/BranchTesting and am seeing an issue with certificates. On all clients, I can run puppetd --masterport=8141 successfully but see the following error when I run against the default (8140) port: err: Could not retrieve configuration: Certificates were not trusted:

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

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:

[Sending this again from the email account that I actually have subscribed to the list - hopefully won't be a dup...] We have been running dovecot-0.99.11-2.EL4.rpm on CentOS4 (since that's the latest that ships with RHEL/CentOS) for a while. Aalso in parallel, we have been running various 1.0 betas and RCs on a different port for a different set of more test-tolerant users. This

Any help would be much appreciated: $refcheck = defined(File["/home/$name/.ssh"]) if $refcheck {} else { file { "/home/${name}/.ssh": ensure => directory, owner => $name, group => $name, mode => 700 } } puppetd says: err: Syntax error at ''File'' at

Has anyone been seeing IO lockup problems on EL4? I've tried multiple IO scheduler options (elevator=) in the boot... I'm seeing the same behavior regardless. Independent of hardware. Whitebox ATA, HA enclosure with dedicated SCSI, megaraid RAID hardware, Dell 2850s... same behavior: A semi-busy system will suddenly go into some kind of IO la-la land where nothing can be written

I get the following error on trying to install mysql rpms please any idea what might be wrong and how to work around it? [root at localhost linux 23-02-2007]# rpm -i --nodeps mysql-5.0.27-1.el4.centos.i386.rpm warning: mysql-5.0.27-1.el4.centos.i386.rpm: V3 DSA signature: NOKEY, key ID 443e1821 file /etc/my.cnf from install of mysql-5.0.27-1.el4.centos conflicts with file from package

I have a client I''m testing where the puppetd process grows slowly (over a few days) to the point where it exceeds 100MB. This triggers an alert and we restart the daemon, but I''m curious whether anyone has noticed similar behavior. Details are: Server: CentOS 4.5 x86 (on VMWare Server guest) RPM install from dlutter repo (puppet-0.23.2-1.el4) The only thing I can

Hello, puppetmasterd is running as shown here: puppet 10209 1.1 1.5 138124 62532 ? Ssl 13:37 0:06 /usr/bin/ruby /usr/sbin/puppetmasterd --manifest=/etc/puppet.production/manifests/site.pp --logdest=/var/log/puppet.production/puppetmasterd.log however, the log file is not being updated with information when a client runs puppetd --test Am I missing something obvious? Best,

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