similar to: Puppet Nodes in DNS

Folks, I have installed puppet my network and it works great .. I have configured it such a way that when I make changes in the server source fiels..it gets updated in teh puppet clients. As the document reads the puppet clients checks for any changes from the server every 30 mins. But is there is any opiton of changing this value to lesser time .. say 15 mins .. or is there opiton for the

I''d like to clarify some points about the ports/package system in FreeBSD. I apoligize ahead of time if this is Both packages and ports use the pkgdb system. This isn''t some lame cludge; it''s by design, and the reason is really quite simple. Packages are built from the ports collection. The only real difference between them is the mode of delivery. When you run

Is it just me, or is reductivelabs unreachable? -- Russell A. Jackson <raj@csub.edu> Network Analyst California State University, Bakersfield QOTD: "It''s been Monday all week today."

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

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"

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

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

The included patch is what I''ve been able to throw together in a few hours after studying the pkgtools code. All I''m using the library for at the moment is to resolve the proper base location of the ports tree, but at least by invoking make directly instead of through portupgrade it works *a lot* better. Is there a proper way to include/require a third party ruby library?

Hi, I''ve set up puppet to get node definitions from LDAP as per the docs. It''s been working well, but I now want to use fully qualified domain names instead of simple domain-less hostnames for the node name. I replaced the ou=Hosts entries with equivalent ones using FQDNs, restarted the puppetmasterd, and tried a "puppetd --test" from one of the nodes. However, I

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

I have the following test case: file { sendmail-conf: path => "/etc/mail/${fqdn}.mc", owner => "root", group => "wheel", mode => 0644, links => follow, source => "puppet:///sendmail/${hostname}.mc" } $mail_dir = "/etc/mail" $cf_dir = "/usr/share/sendmail/cf/" exec { build-conf: command => "/usr/bin/m4

I am attempting to move our test puppet installation from looking for node information in a manifest to LDAP. I followed the instructions at: https://reductivelabs.com/trac/puppet/wiki/LdapNodes and was able to get the puppet schema loaded into our LDAP. I can now query LDAP and modify/load data without any issues using the OpenLDAP tools. e.g. ldapsearch -h ldapdev1.domain.com -x

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

Hello, I recently started deploying puppet on our server farm. It works wonderfully with RHEL4, Gentoo and Debian. I''m looking for a way to determine the state of all nodes. Say for example that I change a file on the puppetmaster which affects 200 nodes. Then I go to lunch. When I get back, I''d like to know which nodes have been updated and which have not. I asked this in

I am trying to configure puppet with LDAP repository . I have set puppet schema and I have also added node definition at LDAP. Here is my configuration details . ############################################################## Puppet.conf node_terminus = ldap ldapserver = 10.250.11.127 ldapbase = ou=Hosts,dc=xyz,dc=com ldapassword = secret

hi, I am from Norway and you'll don't believe me, but a trojan horse in on your pc. I've scanned the network-ports on the internet. (I know, that's illegal) And I have found your pc. Your pc is open on the internet for everybody! Because the smss.exe trojan is running on your system. Check this, open the task manager and try to stop that! You'll see, you can't stop this

I''m trying to get puppetrun to work, without luck so far. I have my puppetmaster and clients working fine with the clients polling the master. Now I want to be able to force an update. Using version 0.23.2 On the client I set listen=true and created the namespaceauth.conf file. Restarted puppetd and it appears fine. On the master I run puppetrun as root and get root@plane:/etc/puppet#

I''m a little confused by the configuration reference. Is the following configuration supposed to work in 0.23.2? # $Id$ 2 3 [main] 4 confdir = <%= confdir %> 5 vardir = <%= vardir %> 6 7 rundir = /var/run 8 logdir = /var/log 9 10 ssldir = $vardir/ssl 11 12 [puppetmasterd] 13 manifestdir = $vardir/manifests 14

I''m using puppet 0.24.7-4. I have a situation where I have some very long running puppet runs in order to do upgrades (removing applications from load balancers gracefully, et cetera). My puppet runs triggered via puppetrun are finishing successfully: Jun 8 20:31:29 puppetd[10178]: Finished catalog run in 345.18 seconds Puppetrun itself is timing out: err: Connection timeout calling

Is there an equivalent to cfrun in puppet. On the cfengine master you can do the command cfrun <hostname> which allows you to tell the cfengine client to run. This is useful for immediately pushing changes out immediately (or telling the client to pull). Chris