similar to: puppetd and self management

Hi, I have several Debian servers with puppet 0.23.2. Part of my manifest looks like this: class virt_all_users { @group { "andy": ensure => "present", gid => "1000" } @user { "andy": ensure => "present", uid => "1000",

Hi, Just a quick query about some things that crop up when I run ''puppetd --test''. Every time I run this command I always see the following output, which I think is strange as the ''man'' package has been installed previously and the firewall service is definitely running. Has anybody got any suggestions as to why puppet thinks it needs to install the man

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

hi,all I want set up a puppet HA structure. but if the puppetd can set more than one server address ,the work will be simple :D if one puppetmaster have error, the client can auto try the next. I think I can use the heartbeat or dns to do this same thing,but not so good. so I want know the puppetd can direct set in the configure file ? if not,will be add this option? -- Huang

Trying to setup a sandbox environment, and I''m running into some issues. When I run the system in --noop mode, everything works as it should (long list of options truncated to ...): [root@kvm001 ~]# puppetd ... --noop info: Caching catalog at /var/lib/puppet/localconfig.yaml notice: Starting catalog run notice: //dev_server/basenode/role_general/ntpd/File[/etc/localtime]/ensure: is

Are exec resources triggered by notify events supposed to be run once for every event received or only run once per run irregardless of the number of resources that notified it? It seems to me that it gets run twice no matter how many resources triggered it. consider the following class: class dhcp { $prefix = "/usr/local/etc/dhcpd" $dhcpd_conf = "$prefix/dhcpd.conf"

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.

Hello, I am rather new to Puppet and am starting to test it out for use on a client''s servers. I am running into difficulty with node behavior. I want to specify a different firewall for every server. The default "basenode" works (applies the various files/functions/etc to all the servers just fine). However, when I specify the following (see nodes.pp, specifically),

hello guys, I am trying to incorporate run stages into my puppet setup. I''ve been working with this for a few days and I haven''t quite got the hang of it yet... When I attempt my puppet run this is the error I see: ------------------------------------------------ [root@chromews21 ~]# puppetd -t err: Could not retrieve catalog from remote server: Error 400 on SERVER:

hi, since my puppet CA expired the nodes cannot connect to the server because of ssl issue. I have recreated a CA and removed/resigned all the certs i could find for the node. However i just saw that the node not having ssl connexion right are still running puppet using cached configuration. Jun 16 03:35:08 xxx puppetd[9503]: Could not get config; using cached copy Jun 16 03:35:10 xxx

Hi All, I asked on IRC but didn''t have everything organized and most people seemed busy. Hoping someone can see what I''m missing here. I''m trying to create a network module, used similar to the ''users'' configuration described in the Best Practices document. I have a users module which has that and it works with similar syntax to below. If I

Hi, I am trying to do my first puppet configuration, already installed the puppetserver and client, in this link show my configuration and my puppet structure: http://paste.pocoo.org/show/212227/ But when i run the client side daemon i get this message: info: /Class[main]/Node[basenode]/Class[inittab]/File[inittab]/source: No specified sources exist err:

i''m having trouble with a file resource with 0.24.1. the manifest is very simple: file { "/": ensure => directory, owner => "root", group => "root", mode => 755 } when i run puppetd, i get the attached stack trace. removing this resource enables puppetd to complete its run successfully. any ideas? didn''t have this

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

I am consistently getting the following error from puppetd when an exec resource is triggered by a refresh event: Apr 23 10:36:11 mailhub puppetd[37884]: Reopening log files Apr 23 10:36:11 mailhub puppetd[37884]: Starting Puppet client version 0.22.3 Apr 23 10:36:11 mailhub puppetd[37884]: Starting configuration run Apr 23 10:36:12 mailhub puppetd[37884]:

Hi, I am getting the following error on my CentOS clients; err: Could not run Puppet configuration client: Invalid parameter stage at /etc/puppet/manifests/nodes.pp:32 The server is CentOS 5.4 with packages from the epel-puppet repos; # rpm -qa | grep puppet puppet-dashboard-1.0.3-3 puppet-2.6.1-0.3.rc3.el5 puppet-server-2.6.1-0.3.rc3.el5 The clients are; # rpm -qa | grep puppet

hi ,all how to update the puppet from 0.22.4 to 0.23.2 . just install it ? is there have some thing need to be be careful ? when update the server and client,all just install the new version ? please help me ,because I use the puppet in product servers,so I need be careful. :D -- Huang Mingyou

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

Greetings all, My deployment of puppet includes a monitrc to make sure that puppetd stays up and running. It seems like (across all of my hosts) that pupeptd will end up dying and restarted by monit. I''m running puppetd under a screen session now on one particular host with --debug --verbose to see if any thing comes out on console but until it happens again, any anybody else