similar to: Puppetd/puppetmasterd crashes when started without --no-daemonize

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I''m running the latest version of puppet (debian 0.22.4-2), and I''ve gotten to a point with my configuration where puppetmasterd needs to be restarted every few days due to what seem like file handles not getting closed. I either see this set of errors: May 22 08:08:34 localhost puppetd[2810]: Could not get config; using

Hi, Since I''ve installed ruby and ruby-gems from source, then installed facter and puppet as gems, I don''t get the usual startup scripts shipped with RPMs. Rebuilding the ruby RPM is painful, mostly because Red Hat (and pretty much every vendor) have this tendency to include random files and patch the living daylights out of a perfectly good source package so that converting

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

Hi, I have a Gentoo server running puppetmasterd from Puppet 0.24.1 and a Ubuntu server running puppetd from Puppet 0.23.2. I have added listen=true to the [puppetd] section on the client and run puppetd --debug. I then run puppetrun --debug --host hostname on the puppetmaster server. This is the output I get: Puppetmaster: # puppetrun --debug --host hostname Failed to load ruby LDAP library.

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

Hi, We have dedicated puppet master boxes, which basically only run a mongrel/puppetmasterd (6 instances), an apache proxy for mongrel and puppetd. Recently puppetmasterds seemed to have leaked almost all of the RAM, and the thrashing made the box painfully slow. We restarted the puppetmasterd processes, and started collecting some statistics. Attached is a graph of memory usage on one of the

Hey all, I have recorded my steps towards getting puppet functional through one of the four different methods that I can think of, which are: 1.Source(copying and insatlling to the recommended unix FSH directory, /usr/local/src) 2.pkg hosted at explanatorygap 3.MacPorts 4.RubyGems I haven''t cleanly tested the last two, but here''s where I am with the first two: 1. I

So when puppetd crashes/whatever, and a pid file is left behind, SMF in Solaris will try restarting puppet, but fail. And then it sits there restarting it forever. I''m not sure if I can adjust the flap detection in SMF.. it isn''t disabling the service for "restarting too quickly" because it takes so long to start. Probably because I''m NFS-mounting ruby. The

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

Is there a way of specifying the server on a different port? I want to be able to change between two different puppetmasterd''s on the same box, and I want to pick between them by using selecting the port. There seems to be lots of :port* symbols floating around, and a --port in puppetd, but it''s not looking consistent. Is this something on the TODO path, or is there a

If you install puppet from the ubuntu 9.04 repositories (apt-get install puppet) it sets up puppet differently than the gem. The differences are obvious from the /etc/puppet/puppet.conf which looks like this [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter pluginsync=true [puppetmasterd]

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

I apologized ahead of time if this post shouldn''t go here but I having been knocking my heading for the last two days trying to get over the following error while trying to "clone" my primary puppetmasterd because we have outgrown one puppetmasterd setup. I have basically set up a 2nd instance of our primary puppetmasterd and rsync''ed over /var/lib/puppet/ssl/ from the

Hi all, I have installed and configure puppet client in new virtual machine, but I have this error when running *puppetd --test (even if I run /etc/init.d/puppet restart) /usr/lib/ruby/1.8/puppet/defaults.rb:136:in `handle'': Invalid environment test (ArgumentError) from /usr/lib/ruby/1.8/puppet/util/settings.rb:299:in `parse'' from

Started the discussion in puppet users mailing list based on recommendation from luke. This discussion is to a follow up regarding bug#1955 "Could not find server puppet" - installation/configuration error". jamtur01''s last recommendation: Rather than renaming things try the certname option (see http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference). But

(I know more questions... :-)) I know the default for puppetd is to check puppetmasterd every half hour, but my question does each puppetd check at the same time? Or does it depend when puppetd is started or like a cronjob does it run at the 1/2 hour and hour mark? Is there some randomness to the times they run? My point is if they all run at the same time then if you have a large amount of

I''m just now getting to testing some things out with puppet and here is my first stab at it. This is in the site.pp file of the puppet server. class test_class { cron { testentry: command => "/usr/sbin/myscript.sh", user => root, hour => 2, minute => 0 } } node leestestbox { include test_class } I''m

Hi all, I''ve just installed puppet in my ubuntu gutsy 7.10 linux using gem: # sudo gem install puppet Then, I made a basic site.pp manifest and following the InstallationGuide I ran: $ sudo puppetmasterd --mkusers Could not configure for running; got 1 failure(s) What error? I managed to get an error message on /var/log/daemon.log Jan 30 16:22:13 acero puppetmasterd[13800]: