similar to: Fileserver Issue

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

While running puppetd on a linux client I get the following, the actual spot that the segfault happens varies, but it always happens. This is on ubuntu with the stock apt ruby1.8.4 package. Puppet also installed from apt. Puppet version 0.18.4 It seems very likely that this isnt a bug in puppet per se, but it is tickling a yaml bug (regardless of where it fails, it is always yaml). But I

Hello all, I have a little problem with the --listen option. Id like my client servers to update only when I run puppetrun on the puppetmaster server. So far, I tried: puppetd --listen --server mymasterserver -v (on the client server) Then: puppetrun --host myclientserver The updates runs ok... but the client check for updates again every 30 mins or so and I dont want him to do so. I tried:

OS: FreeBSD 6.2-RELEASE Puppet: 0.22.4 OS: CentOS 5.0 Puppet: 0.23.2 Is it currently not possible for puppetd to upgrade itself (0.22.4 -> 0.23.2)? I tried it, and when puppetd attempted to restart itself (using the init provider), it failed to start back up. Perhaps the init provider needs to close all file handles before executing the rc.d scripts? Additionally, I had puppetd update its

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,

hello, we just wanted to rollout our new puppetized dmz. therefore i change all ip adresses from the test network to the live ips. after restarting puppetmasterd it seems that the fileserver hangs: client log: debug: //true_base/update-check/File[/sbin/update_check.pl]/require: requires Package[libmail-sendmail-perl] debug: //true_base/puppetd/File[/etc/puppet/puppetd.conf]/require: requires

Hi When using puppetrun to trigger machines to get and apply their configuration, it will only trigger the machine when executing puppetrun for the second time: puppetmaster # puppetrun --host puppetclient puppetclient log: -- snip Apr 13 08:19:49 puppetd[20208]: puppetmaster(172.16.34.12) triggered run Apr 13 08:20:08 puppetd[20208]: puppetmaster(172.16.34.12) triggered run Apr 13 08:20:08

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

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

I configured my rsync daemon to be restarted when the rsyncd configuration file changes. When the rsync daemon gets restarted by puppet, it listens on the same port puppetd does, so running puppetd again results in an error. The init script for rsync is small and can not be changed from puppet (all variables are declared within the init script and it only searches for the path where the rsync

> 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

Hi all, I''m having trouble with a particular recipe, but I don''t know which one! I''m not getting an error message, puppetd simply hangs (does not respond, needs a kill -9 to stop). These same recipes work correctly on other nodes (no problems there). Now I wanted to find the exact line that causes the problem, but I seem to be unable to make puppetd log the resource

Sorry if this is obvious, but how can I have reports emailed to me- I want to know what each puppetd update is changing Thanks --e Eugene Ventimiglia Director of Systems GridApp Systems e: eventi@gridapp.com o: 646 452 4081 _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

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

I am consistently getting the following error from puppetd when an exec resource is triggered by a refresh event: Apr 23 10:36:11 mailhub puppetd[37884]: Reopening log files Apr 23 10:36:11 mailhub puppetd[37884]: Starting Puppet client version 0.22.3 Apr 23 10:36:11 mailhub puppetd[37884]: Starting configuration run Apr 23 10:36:12 mailhub puppetd[37884]:

Hey All, Id like to submit two init scripts for debian for puppetd and puppetmasterd, Which is the best to do this? Cheers B _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

So I''ve done some Mac OS X pkgs for the latest Facter and Puppet, as well as a combined mpkg for them both. Jeff McCune and I are doing a fair bit of testing on them this week in preparation for MacWorld, so I wasn''t going to upload them to the official site for another few days, but they''re looking pretty good. http://explanatorygap.net/puppet/Facter_1.3.8.pkg.zip

i''m having trouble with a file resource with 0.24.1. the manifest is very simple: file { "/": ensure => directory, owner => "root", group => "root", mode => 755 } when i run puppetd, i get the attached stack trace. removing this resource enables puppetd to complete its run successfully. any ideas? didn''t have this

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

I recently had a working puppet server serving around 4-5 clients. One of the clients needed to be re-built and now only that client cannot connect. puppetca --clean hostname did not work So here is what I did on both the server/client I removed /var/lib/puppet/* Then I restarted the server via puppetmasterd --mkusers --verbose I then connect in via the client with /usr/bin/ruby