similar to: puppetmaster 0.25.x factdir error

Hello... I noticed that puppet is not in the FreeBSD ports collection. Is anyone working on adding it? Or has someone made a ports Makefile for local use they can share? -- Christopher McCrory "The guy that keeps the servers running" chrismcc@pricegrabber.com http://www.pricegrabber.com Let''s face it, there''s no Hollow Earth, no robots, and no ''mute

Hello... After a break, I am back to my integrating puppet project. While testing I ran into a bug in puppetmaster.log. (maybe. it is possible I did this myself with a borked config ) I seems that puppetmaster is re-logging past data. I have noop = true and set runinterval = 60 to show the bug. I manually added the "manual break" lines in between runs. Wed Jan 24 09:27:29

Hi folks, When I enabled stored configs on my puppet master, it began keeping lots of open connections to the MySQL server (as far as I understand it opened one connection for each client run and never closed them). I set up the server to close idle connections after 5 minutes. Now the database server does close the connections but the puppet master keeps them in CLOSE_WAIT state and eventually

Hello... I am looking to replace my current config file management solution with puppet. I looked at both cfengine and puppet and neither seem to have a "diff" option. as in: configfile { "/etc/httpd/conf/httpd.conf": source => "/httpd/httpd.conf" } will install a httpd.conf file. What I would like is to be able to see a unified diff of the

Sorry to bust in, folks, but I'm having some trouble integrating the OpenSSH RPMs in my Red Hat 6.1 system and was hoping somebody could point me at an appropriate place to ask my newbie questions. (I've been over the docs and they don't seem to apply to the problems I'm having.) -- http://www.pricegrabber.com | The best deals, all the time.

I have several machines that must have trusted root accounts, that is, I need to be able to run "ssh targethost command" on each by each, for the root user. I have had no success thus far doing so. Normally for the non-root users, all I have to do is set the /etc/ssh/known_hosts, build up the users' ~/.ssh/known_hosts, and the users will work without requiring passwords. (I'm

This is on rsync v2.4.5 on RedHat 7.3. If I do something like rsync ... 'somehost:/path/to/files.*' /local/path it works fine, but if I do rsync ... '/local/path/to/files.*' somehost:/path/to globbing fails, yielding an error about being unable to find a file named 'files.*': link_stat /local/path/to/files.* : No such file or directory rsync error: partial

Hello... In regards to http://www.freebsd.org/security/ , from what I understand the FreeBSD 4.x branch is generally winding down in favor of the 5.x/6.x branches. It would be nice to know ahead of time if 4.11 will also be an extended release, or if that would fall to 4.12. For those of running 4.8 (expiring about the same time as 4.11 is released) we would be in a better position to know

Facter has the feature that it will turn any environment variable named FACTER_* into a fact. I can do this on the commandline no problem, but when I attempt this in puppet it seems to ignore that parts. Is anyone else seeing this? (Is this expected behavior?) I don''t see a ticket or a mail thread on it - though my searching powers have been weak the last couple of weeks... Thanks,

Is there any way to do a simple search and replace on the puppetmaster server? I''m passing one IP address for one interface on a box, and attempting to set the second according to a convention we use, so I need something like $eth1_ip = `echo "10.100.6.99" | sed -r -e ''s/\.[0-9]+\.([0-9]+)$/.94.\1/''` # eth1_ip = 10.100.94.99 interface {

hi,all. I found a interesting problem. first ,a new node run the puppetd to connect the puppet server, then was treated as "default" node. that''s right. Then I add the new node''s hostname in a node define. and run the puppetd ,is still get the default manifests file. But when I restart the pupppuetmaster, then it can get the new manifests file to correspond

I''m getting the following error when trying to run puppetd on the server. I''m using version 0.23.2 from the dlutter repo. The OS is RHEL 5. Any idea what this is? I see reference to namespaceauth.conf regarding this problem but I can''t find anything definitive. [puppet]# puppetd -v -o err: Could not call puppetmaster.freshness: #<RuntimeError: HTTP-Error: 500

Hello, i used puppetd --genmanifest to create a site.pp and it created some weird entry: file { ''/var/puppet/log'': group => ''puppet'', loglevel => ''debug'', owner => ''puppet'', backup => ''false'', mode => ''488'', ensure =>

My setup is as follows: I am running Vmware Server on Ubuntu Feisty. This is the puppetmaster. I am running a guest of Ubuntu Gutsy. This is the puppet. When I try to run puppetd on the guest I get the expected message "notice: Did not recieve certificate" Going back to the server and running "puppetca --list" does not list any requests. As a hunch I telneted the hosts

Hi all, we had notified that table ''fact_values'' of puppetmaster database is not updating when a fact value changes (for example we have updated some puppet clients version to 0.23 and fact_value of database is still the old version 0.22.4) it is a bug? misconfiguration? we are using ''storeconfigs = true'' with MySQL backend we''ve tried to restart

So one of the behaviors that seems to wedge puppetmasterd is if you re-initialize a client, the example here being that I installed an older version of puppet on a bunch of machines to test out how things work: * at some point in the past install older rev of puppet - client regiesters itself with the server, etc. - works fine. * recently, remove the old puppet in favor of a new version that

What''s this mean? root@gravity:/etc/puppet/manifests# puppetd -v --listen info: Starting handler for Runner info: Starting server for Puppet version 0.22.1 info: Listening on port 8139 notice: Starting Puppet client version 0.22.1 err: Could not run Puppet::Client::MasterClient: Host gravity.example.org not authorized to call puppetmaster.freshness Thanks, Kent -- "It may be true

I''m trying to load balance multiple puppetmasters using apache and passenger as described in James''s book. Was able to get a single passenger server installation to work correctly. When I configure the frontend load balancer and backend workers, the backend workers does not authenticate even though I am passing the headers to it. curl -v -H "Accept: pson, yaml" \

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''m unable to get a response from the puppetmaster I''m testing with. `netstat -apn` shows puppetmaster/ruby listening on port 8140, but telnet connections are refused both from a different location and from the commandline on the master server. I''ve restarted a number of times but I''m still getting nothing, and AFAICT there aren''t any conflicting