similar to: core dump

I''m trying to manage network files on two nodes, "vico" and "backup." The component "vico_network" below works fine. define vico_network ($owner = ''root'', $group = ''wheel'', $mode = ''644'', $cro_int = ''ne3'', $carp0_skew = '''', $carp1_skew =

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

How can I express the following in puppet? $http_conf = "/etc/http/conf/httpd.conf" $vhosts_conf = "/etc/http/conf/vhosts.conf" @files = ("$httpd_conf", "$vhosts_conf") foreach f (@files) { file { "$f": owner => root, group => root, mode => 664, source => "puppet://$server/apache/$f", }

OK, I started down this road a few months ago and got side tracked with project work. I have a class called "install" that I want to use with only machines on one protected subnet. In my site.pp file, among other node entries, I have - node default { install } The class itself - class install { case $domain { "test.example.com": { file:

I''ve tried this on two different setups all running 0.22.1. One group is Ubuntu/OpenBSD the other is RHEL4/RHEL4. Master has signed client certs. puppetd works fine from client. If I run from the server side: root@server:~# puppetrun --host client_host.example.com Failed to load ruby LDAP library. LDAP functionality will not be available Triggering client_host.example.com Host

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

I''ve submitted the following to howtoforge.com for approval. My plan is to create similar docs for OpenBSD, RHEL and installing from source. I''d certainly appreciate comments on how to improve the document, and feedback on errors. http://nixnotes.org/puppet.html Kent -- "It may be true that the law cannot make a man love me, but it can stop him from lynching me, and I

The following works fine but is there some way to make it more succinct? Thanks, Kent class obsd_etc_static { file { "/etc/mygate": owner => root, group => wheel, mode => 644, backup => main, source => "puppet://example.com/obsd_static/mygate" } file { "/etc/rc.conf": owner => root, group => wheel,

Can you wildcard a domain for a node name like the following? node ''*.sub.example.com'' { .... } Thanks, Kent

I''m trying to come up with a way to manage /etc/puppet on the Puppet server from my workstation. My idea was to place all of /etc/puppet into subversion, check it out to my workstation, commit via ssh, and then use a post-commit to update /etc/puppet. That way any time I made a change in /etc/puppet it would be immediately updated and ready for the next puppetd run. Problem is the

Is anyone having problems with running Puppet 0.22.1 on Edgy? I installed the puppet and facter packages from Fiesty and I get core dumps when I try to run puppetd on the machine. Prior to that I was using 0.20.1 packages from Debian testing and all seemed well. I posted about the core dump yesterday. Luke recommended upgrading Ruby so I grabbed ruby-1.8.5-p12 source and installed. The prior

I just built new puppet rpm''s for Fedora (puppet-0.22.1-2) that fix the lockdir problem that many of you have encountered. The packages should show up on a mirror near you very soon. Unfortunately, I am having trouble getting to my buildsystem that I use for the RHEL versions of the RPM; I made the source rpm available on my people page[1] If you need the RPM for RHEL, you need to

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

Below is a simplified version of a class I''m using. I found that using a single character in the case statement results in the following error. [root@puppet classes]# puppetd -v -o notice: Ignoring --listen on onetime run info: Facts have changed; recompiling err: Could not retrieve configuration: Invalid tag "w"

Hello all, puppet hangs while trying to restart a daemon when the associated config file changes, here the log: Mar 19 11:30:04 ingentTest puppetd[27390]: Starting Puppet client version 0.22.0 puppetd[27390]: Starting configuration run puppetd[27390]: (/ingenttest/qualsevolnode/guaita[guaita]/File[/etc/guaita.conf]/content) synced puppetd[27390]:

Hello, I have recently run across the following error: /usr/lib/ruby/1.8/yaml/rubytypes.rb:315: [BUG] Segmentation fault This has happened after adding a particularly large template file with ruby 1.8.1. Thank you, -- Rob -- ____________________________________________________________________________________ Be a PS3 game guru. Get your game face on with the latest PS3 news and previews

Greetings - I''ve just started testing Puppet and have a couple of questions: 1. Is there a way to dynamically change a configuraion file that is sent to nodes? For example, I want to modify /etc/hosts to have the hostname and ip address set dynamically - the hosts file shoule look like: 12.34.56.78 node1.example.com 22.35.66.99 server1.example.com But I don''t want to

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

I just upgraded from 0.23.2-1 on RHEL 4&5 to 0.24.1-1. I used Dlutter''s repository. What a mess I''m in now. Anyway to make a long story short I moved all of the old configs out of the way (/etc/puppet, /var/lib/puppet) and started over with a fresh install. I can''t get puppetd on the server to request a cert. If I do a "puppetd -v --waitforcert 90" the

I recently had a working puppet server serving around 4-5 clients. One of the clients needed to be re-built and now only that client cannot connect. puppetca --clean hostname did not work So here is what I did on both the server/client I removed /var/lib/puppet/* Then I restarted the server via puppetmasterd --mkusers --verbose I then connect in via the client with /usr/bin/ruby