similar to: puppetd by cron using cached config , does it expire ?

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

It appears that --report only works to send reports to puppetmaster. Is there a way or could an option be added to have the puppet client print out it''s report to stdout or stderr, for folks who are using puppet without the puppetmaster/puppetd? Thanks, Abe _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com

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

> -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of Johnny Hughes > Sent: den 26 maj 2016 14:30 > To: centos at centos.org > Subject: Re: [CentOS] Kernel panic on 6.8 release with kernel-2.6.32- > 642.el6.x86_64 > > If lockd is failling to start: > > https://bugs.centos.org/view.php?id=10927

Greetings, I''ve two questions for y''all. 1) I''ve setup an alternate installation path for puppet in a site local directory outside of ''the usual places''. Puppetd seems to insist that /etc/puppet/namespaceauth.conf exists despite setting :authconfig in both puppet and puppetd. As a result part of my installation now includes a symlink to point

Hi, I''m running multiple vservers and have some aspects managed via puppet. I noticed that puppetd consumes from 20 to 60 mb RAM and the longer the process runs, the more RAM it takes. It looks like 60MB is the top what I measured. Having a couple of vservers (11 in my case) this can already take up to 500MB just for puppet! I''m wondering if there''s any downside in

i wonder why this case fail: case puppetversion { ''0.22.4'':{ #ok notice(''ok bonne version'') } default:{ fail("mauvaise version de puppet $puppetversion, downgrade vers 0.22.4") } } gives me: protos:/usr/local/.aqadmin/home%(aqadmin)> facter puppetversion 0.22.4

I've cross-compiled flac for the armv4l processor (rio receiver), and i'm trying to start up a decode thread : #include <FLAC/stream_decoder.h> .... FLAC__StreamDecoder *flac = NULL; flac = FLAC__stream_decoder_new(); if (flac == NULL) { printf("[DECODE] Unable to initalize flac object\n");

dear all I have a postfix relaying to dovecot's lda but "strangely" it does not work, I mean I imaging it's me doing something wrong, yet I cannot figure out what. postfix logs: to=<me at my.domain>,orig_to=<root at localhost>, relay=dovecot, delay=39296, delays=39294/2.2/0/0.27, dsn=4.3.0, status=deferred (temporary failure) and dovecot logs no error, despite

hi, i am new to ruby on rails. when my box is connected with the net, i am able to install rails easily with remote option, but i am failling to install it locally (given that my box is not connected to internet). I have downloaded rails library. Please some one tell me how can i install it locally thanks -- Posted via http://www.ruby-forum.com/.

Hello, I noticed some random crashes after sending SIGHUP to the daemon (especially when some connections are continually failling). Playing around with gdb, it seems that after SIGHUP, all the "outgoing" information of the connections is being cleared, but later on it is being used in other places while still equal to NULL. The attached patch tries to fix this by avoiding these

Hello all, I am new to puppet and I currently just use it during development - just two hosts. I only manage distribution of files/permissions with it. I am wondering why puppetd is running slowly on one of these machines. Google told me that File with "recurse => true" will make things run slowly. I use "recurse => true" :( Now I want to find out now if the slowdown I

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

On the Configuration refrence page the listen setting is descriped thusly: listen Whether puppetd should listen for connections. If this is true, then by default only the runner server is started, which allows remote authorized and authenticated nodes to connect and trigger puppetd runs. The question is when listen is set to true, does puppetd only listen for remote calls or will it listen for

This feels like a FAQ and sorry if it is, I failed to find an answer. I''d like some advice on handling backward compatibility between puppetd and puppetmaster. My puppetmaster is at v0.24.5 using Debian Lenny packages. I tried to bring up a puppetd client v0.25.4 (Ubuntu 10.04 packages) but failed to have it download the puppetmaster''s certificate. The puppetd client seemed

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

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