search for: puppetds

Hi- Recently starting using puppet while migrating an existing messy group of systems to some nice new hardware. Things are going incredibly well, and puppet''s functioning great. Have a bit of a headache. I''d like to keep myself from duplicating lots of included classes. Lets say I have this (snippet of a) class: class dbserver { file { "/etc/my_${db}.cnf":

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

hi, i''m trying to set up my puppetmaster infrastructure with multiple puppetservers behind load balancers in each of our datacenters. i''m using 0.24.6. i''ve read the howto on puppet scalability, and i think i''ve got the ssl config working correct, but i''m noticing that when puppetd is used to build a puppetmaster, some of the files in $vardir/ ssl

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

Here is my class class puppetconf { file { "/etc/puppet/puppetd.conf": mode => 644, owner => root, group => root, source => "puppet://puppet/cci/etc/puppet/puppetd.conf", notify => exec[puppet_restart] } file { "/etc/init.d/puppet": mode => 755, owner => root, group => root,

Hi, installing puppet at my first site was quite easy (not w/o problems, but still). At the second site, I''ve run into something more serious. First things first - I install puppetmaster on existing server, used to keep LDAP db (my puppetmaster DOES NOT use LDAP, it just tries to coexist on the same machine). The thing is, I need to puppet this baby, so I''m running into a

Hi guys, Unlike what it says in the documentation and the --help output, I can''t seem to get puppetd to use the --server setting. The only way I can get puppetd to work is to include a ''puppet'' alias to the ip of the machine I''m running puppetmasterd on in my hosts file. The strange thing though, is that the logs of my puppetmaster show that it *is* getting

Greetings all, My deployment of puppet includes a monitrc to make sure that puppetd stays up and running. It seems like (across all of my hosts) that pupeptd will end up dying and restarted by monit. I''m running puppetd under a screen session now on one particular host with --debug --verbose to see if any thing comes out on console but until it happens again, any anybody else

I''m having this issue where "puppetd -v -o" hangs (won''t return my prompt) when starting a daemon I wrote. If puppetd is running as a daemon a zombie process is created each time puppetd tries to start my daemon. Puppet detects when the daemon is down and starts it just fine. I''m using version 0.22.3 on RHEL 5. Here''s the class. I''ve

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

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

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

I just started playing with puppet. Unfortunately, it keeps crashing in a variety of places. I don''t have much experience with Ruby yet, so any tips in tracking down these problems would be appreciated. I''m using the Debian package 0.18.4-1. Here''s the output of a couple runs: www01:/home/cwarden# puppetd --verbose --onetime info: Caching configuration at

Guys, I seriously could not find this topic in the documentation. What do you do when you need to force puppetd hosts get the new settings from puppetmasterd? What I found was only sending USR1 signal to the client process in order to make it refresh its configuration from the master. But I find it a bit inconvenient for a large amount of hosts. There is also puppetrun which, if I understand

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,

Heya, I''m using puppet on Ubuntu (Gutsy/Hardy) and there''s a problem with the default setup of Ubuntu. Ubuntu uses network-manager to start the network in the background, which in turn causes puppet to start before the network is up. Puppet will then exit because it can''t resolve the server name. Currently I "solve" this problem by uninstalling

I''ve got the following class that runs if I activate the repo in /etc/yum.conf. If I run "puppetd -t" from the command line it will restart puppetd fine. If I let the class run on it''s own as a deamon puppetd does not restart. The puppetmaster on the other hand does restart using either method. I ran the client in "--debug" but that doesn''t seem to

Hi, From looking at the puppetd --help, there is not currently (at 0.22.4) a method of specifying tags in the puppetd.conf. I was hoping to use this for the following reason: Currently, I use ''noop = true'' in my puppetd.conf, and run ''puppetd --no-noop {tags}'' to install the configurations that I am happy with. This is because I''m currently

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

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