similar to: The /var/lib/puppet/clientbucket directory grew 4GB in minutes, filling up /var on production server

Hi all, I''m doing a new install of my puppet server and I''m doing it like: 1.-) adding epel repo: http://fedoraproject.org/wiki/EPEL/FAQ#howtouse 2.-) yum -y install puppet-server 3.-) rm -rf /etc/puppet 4.-) copy my old puppet conf (from puppet-0.24.5 to 0.24.6) mv /etc/puppet.old /etc/puppet 5.-) start puppetmaster: [gridinstall etc]# /etc/init.d/puppetmaster start

Is there a way to copy file(s) from the Puppet agent back to the master? I know it sounds silly but that''s what I need to do. This is one of the s/w-tag files, gets created/modified automatically by the software installation job and then I want to overwrite the tag files on two other agents with this one. Is there a why for doing this? Cheers, San -- You received this message because

Hi everyone, I''ve got several questions that are most probably obvious to some of you but I''m actually a bit ''in the fog'' about filebucket. backup are done on a md5 basis so 1 file is generated whatever the number of clients if it''s the same md5. That a really good option. On the other hand let''s say that after 3 months I need to restore a /

Is puppet --genmanifest something one should still be using? I''m having some problems running it on RHEL4 and I''m sure I have read something about puppet taking care of its own directories automatically. Here are a selection of problems This entry stops puppet from running, (reported by Ben Abnormaliti@clivepeeters.com.au) file {

In my puppet client I have puppet.conf defined puppet server as mypuppet server = mypuppet.example.net Not sure why the puppet client puppet-test is still sending these noises to the syslog Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911 daemon.error] Could not find server : getaddrinfo: node name or service name not known Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911

I am having issues with filebucket. I have looked through the puppet users google groups with similar issues but have not found a solution that works. I am trying to setup a central filebucket on the puppetmaster server. I am replacing the client''s /etc/puppet/puppet.conf file with a preconfigured version. The server delivers a copy of the puppet.conf file to the client, but the backup

whenever i run a test from client it finishes sucessfully but client is not getting any configuration changes from server [root@PROXY-02 tmp]# puppetd --noop --test notice: Ignoring --listen on onetime run info: Caching catalog for proxy-02.carnation.in info: Applying configuration version ''1327091881'' notice: Finished catalog run in 0.02 seconds [root@PROXY-03 modules]# puppet

Hi all, I''m having a stupid moment getting a remote file bucket working. My client only file buckets locally, not remotely. I have this site.pp: ********* filebucket { "main": server => "puppet" } File { backup => "main" } node ''default'' { include test } ********* and this test module: ********* class test { file {

I''ve been confused by this question for near two days ...my puppet master version is 2.7.9-1.el6 and client versiong is 2.6.16-2.el5. This is what my command lines shows: *[root@agent1 ~]# puppet agent --server=edward --test --waitforce 30* info: Creating a new SSL key for agent1 warning: peer certificate won''t be verified in this SSL session info: Caching certificate for ca

Hi. When running "puppetd --server <puppetmaster> --waitforcert 50 --test" on a puppet client we get the following error: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': getaddrinfo: Name or service not known (SocketError) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect''

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''ve noticed that on servers that are both puppet and LDAP clients, the puppet client will hang if the LDAP server is not reachable. Does anyone know what the reason for this is? Regards, Kenneth Holter --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this

Greetings all, (Hopefully this won''t be a HTML mail.) I''ve picked up puppet as a tool to manage a fairly small network of RHEL servers, and I''m really liking what I see so far. However, I''m having a pile of trouble with a class definition for a yum controller: # $Id$ class yum-rhel5 { file { "/etc/yum.conf": mode => 644,

If anybody knows? plese tell me what is a reason of this problem, i`m novice with puppet and sorry for my english=) have error on client: [root@node13 ~]# [root@node13 ~]# puppet agent --server=head02 --test warning: peer certificate won''t be verified in this SSL session warning: peer certificate won''t be verified in this SSL session info: Creating a new SSL certificate request

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

Hello all, I''d like to have Puppet distributing one of your server''s (public) SSH keys, effectively doing the same as the ssh-copy-id command. Is there a build in puppet resource type for managing SSH keys. We''re running version 0.24.4 of puppet. Regards, Kenneth Holter --~--~---------~--~----~------------~-------~--~----~ You received this message because you are

Hi, I created a centOS6 EC2 instance last night and ran the foreman puppet module but it came back with a few years. Was hoping somebody could help me understand these errors. [root@ip-10-170-77-129 config]# echo include foreman | puppet --modulepath /root/puppet-foreman/ err: /Stage[main]/Foreman::Config::Enc/File[/var/lib/puppet/yaml/foreman]/ensure: change from absent to directory failed:

Hi all. We have a bunch of RHEL servers running Puppet. They are also connected to our Red Hat Satellite server. Currently we don''t have any master documentation system that stores all relevant information (i.e. type of server, hardware info, linux configuration, etc) about the servers. So what I''d like to do is implement some sort of system that can hold all this information.

Hi all, The last 2 weeks we have been having problems with puppetd just randomly stopping. The only thing the log shows is: <snip> Apr 21 12:14:59 relay puppetd[1376]: Finished catalog run in 4.78 seconds Apr 21 12:30:07 relay puppetd[1376]: Finished catalog run in 4.76 seconds Apr 21 12:45:20 relay puppetd[1376]: Finished catalog run in 4.61 seconds </snip> There is no pattern when

Hi all, Could anyone help me at least start debugging this issue? All agents have the same error, but i can''t find anything on the master-side logs. And the agent-side logs are non-existent (/var/log/puppet is empty). Thanks. Versions: Master: Red Hat Enterprise Linux Server release 6.3 puppet-server-3.1.0-1.el6.noarch puppetdb-1.1.1-1.el6.noarch puppetdb-terminus-1.1.1-1.el6.noarch