search for: puppetmasterds

Hi Guys, Im trying to turn on storeconfigs with a mysql db backend. On my testing server in our lab, i configured this successfully and can see if keeping information on all test hosts. When trying to implent the same idea onto our production puppet server, I get the following errors: Aug 26 16:35:53 opsynxsr0097 puppetmasterd[27003]: (/Settings[/etc/

Hi, I''ve installed puppet gem on freebsd 6.1 and wrote a simple startup script for puppetmasterd. It starts fine, but doesn''t create the pidfile, so I can''t stop it. Here is my script: #!/bin/sh utility_enable=${utility_enable-"NO"} utility_flags=${utility_flags-""} utility_pidfile=${utility_pidfile-"/var/run/puppetmasterd.pid"} .

After reading the rc.subr(8) man page and Newburns''s article on the rc.d subsystem[1], It''s clear that a rc.conf.d per service file structure is already natively supported on FreeBSD. I''ve verified this with my own testing: # echo puppetmasterd_enable=\"YES\" > /etc/rc.conf.d/puppetmasterd # /usr/local/etc/rc.d/puppetmasterd start Performing sanity check

Getting some strange behavior when I try and start the puppetmaster. I keep my configs in a subversion repository so naturally there are .svn directories within the puppet config directory. Not sure why but one of my puppetmaster instances refuses to start until I remove one specific .svn directory. No puppet process running. [root@puppethc01 files]# ps -ef | grep puppet root 16417 13135 0

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 there, I''m running puppetmasterd manually while testing, and I was trying to split my manifest in several parts using import. If I do so whenever I run the puppetmasterd the manifest gets loaded and served correctly: cognos ~ # puppetmasterd -v info: Starting server for Puppet version 0.20.0 info: Parsed manifest in 0.02 seconds info: /var/lib/puppet/files: allowing *.example.org

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 Folks, Just wondering what the above error means. I followed the instructions in http://www.howtoforge.com/installing_puppet_on_ubuntu and when I try to startup the server it fails with the error in the subject of this message. I am running the server on Ubuntu/i386/gutsy. In particular, # puppetmasterd --verbose --debug debug: puppetmasterd: Setting logdir to

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 boxes over two weeks or so. Remarks: * The restart happened on the 21st....

Hey, Just wondering if anyone else has noticed this. I''m using thin+puppetmasterd+nginx. If i add a host, sign it''s key, run puppetd successfully on it all is good, as expected. If i then revoke/clean the key on the master server, leave the box running, startup another host set the hostname to be the same as the old, generate new keys/have them signed. The original box is still

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 all, I have experience using puppet, however I am new to setting puppet up as it was already done for me in past environments. I am running into an issue while trying to set puppet up for the first time on RHEL 6.4. I was hoping y''all might be able to help me! I get the following error from the puppet client''s /var/log/messages log: May 30 07:06:30 pclient

Is there any "correct" way to get puppetmasterd to not spam syslog with (mount[blah]) File source foo does not exist messages when using file source selection lists? I use them quite extensively, so it''s getting quite out of hand. The last resort will be to comment out the offending print statement! -- Russell A. Jackson <raj@csub.edu> Network Analyst California State

Hi there I would like to setup my puppetmasterd behind my ADSL modem and manage the nodes on the hosting sites. I can imagine opening ports to the puppetmasterd server will work. Am I right? On the other hand an ideal configuration for me would be a Reverse Proxy setup, so I don''t have to touch the ADSL router. Has anyone setup a puppetmasterd behind a reverse proxy? Any pointers,

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

Hi Puppet-Team, first thanks for this great configuration management tool ! My name is Matt and i am on creating a puppet plugin for openQRM. The basic framework is already existing and working well so far. Now, after having it working ok once i now ran into a problem that my puppet-clients do not get their configuration any more from the puppetmasterd. What i saw on the puppetmasterd logs is :

Hi, I''m just getting started with puppet, and using the RPMS provided (on CentOS 4.3), and RedHat''s killproc is annoying me again. The process is called ''ruby'' instead of ''puppetmasterd''. $ ps 7869 PID TTY STAT TIME COMMAND 7869 ? Ss 0:00 ruby /usr/sbin/puppetmasterd [ etc ] So, service puppetmaster

Hi all, This has theoretically been a high priority for a long time, and I''m finally going to get it done, I think. Here''s my plan, and I''d appreciate any comments you might have on it. Currently, sections only have meaning internally, in that one can call ''config.use(section)'' to create any directories needed for that section. Additionally,

I left my new puppetmasterd running last night. came in with a stack trace below. A number of questions: 1. Where did /Settings come from? 2. Is there a way to dump the contents of the catalog to understand? 3. I want to change the perms for all that stuff 4. puppetd is not running on this host, does puppetmasterd act like a puppetd? notice: Compiled catalog for inst01.corp.631h.metaweb.com

Hi everyone, I am in the process of evaluating Puppet (version 0.23.0 - Solaris 10 sparc), so I am still a newbie. First tests with Puppet were fine since it was running with the default configuration. Now, I have created a "puppet.conf" file ( puppetmasterd --genconfig > puppet.conf ) to customize some of the configuration parameters. When "puppet.conf" is present,