similar to: Do we need a new name for "--test"?

Displaying 20 results from an estimated 30000 matches similar to: "Do we need a new name for "--test"?"

2010 Oct 05
32
puppet push mode
Hello All, I am trying to put puppet into push mode only. The instructions I''ve seen have said to put listen=true in puppet.conf but that doesn''t seem to have stopped the pull every 30 minutes. What else needs to be set? Thanks, Jim -- “Twenty years from now you will be more disappointed by the things that you didn’t do than by the ones you did do. So throw off the bowlines.
2010 Nov 07
14
EC2 with puppet bootstrap notes and scripts
Hello... I wanted to be able to startup an EC2 instance with one command and have a fully functioning server without having to shell into each new instance and configure the bits to allow puppet to finish the configuration. Here are some notes I came up with for bootstrapping an ec2 instance with puppet using Ubuntu 10.04. I left out a lot of things about creating and running custom AIM
2010 Dec 06
7
error running puppetrun
Hi, I have been getting the below error for sometime now. Both master and client are using version 0.24.8. Output from /var/log/messages err: Could not call puppetmaster.getconfig: #<#<Class:0xb7b50a9c>: execution expired> err: Could not retrieve catalog: execution expired P.S- all of this was working absolutely fine and suddenly has started to misbehave. Regards, -- You
2012 Feb 08
10
puppetd hanging on some nodes
Hi All, In my set-up, I''ve got a cron job that triggers a Puppet run every 20 minutes. I''ve found that on approximately 13 nodes (out of 166), puppetd just hangs. I have to go in, kill the process, remove /var/lib/puppet/state/puppetdlock, and run puppet again and then it''s fine. After a while, it just hangs again so I have to go in, kill the process, etc. Any ideas?
2009 Jul 13
7
puppetd no-daemonize
So I have been trying to run puppet once in my kickstart %post scripts but every time it detaches and daemonizes even though I have explicitly stated otherwise. Am I missing something? # rpm -q puppet puppet-0.24.8-1 # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug debug: Creating default schedules debug: Failed to load library ''shadow'' for feature
2012 Aug 23
1
Puppet Agent VS User
Hello, Running into a problem when wanting to daemon-ize the agent. It doesnt seems to do anything: - cannot find any daemon process with (ps aux | grep puppet) - the config is not updated after editing some params on the master - /var/log/puppet stay empty... while, when logged as root, it is working without issue with $puppet agent --test. ##Conf Ubuntu 12.04 Puppet 2.7.11 ## Daemon is
2010 Nov 11
9
preferred directory structure for multiple environments
Hello All, Moving from 2.5 to 2.6.2 and I was wondering if there is a preferred directory structure for using multiple environments? Does it work much different in 2.6 than in 2.5? When I made the move I assumed (I know) that my current structure and configurations would just roll over but that isn''t the case. Thanks, Jim -- You received this message because you are subscribed to the
2010 Oct 20
9
puppetd 0.25.4 with puppetmaster 0.24.8?
Our puppetmaster runs 0.24.8 on Ubuntu 9.10. Our clients are either Ubuntu 9.10 or Ubuntu 8.04. We''ve just brought up our first Ubuntu 10.04 machine. This machine installs puppetd 0.25.4. The Ubuntu 10.04 machine can''t seem to present it''s certificate request properly. In my masterhttp.log, I see [2010-10-20 13:09:06] 174-143-141-55.static.cloud-ips.com - -
2009 Nov 12
6
Multiple environments
So I''m trying to get multiple environments to work with puppet 0.25.1 on ubuntu 8.04 and no matter what I do, puppet just completely ignores any environment setting. There''s really next to no information in terms of configuration on the multiple environments documentation page (http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments) other than saying that the
2009 Jun 16
4
Schedule puppet runs
Hi All, I would like to pick your brains as to the best way to configure the below senario within puppet. I am currently configuring puppet for our environment and have seperated development/back office from production through configuring roles for each server to identify them as such. What i need to be able todo is have the production servers only update outside of office hours, but have the
2012 Jul 18
4
cert issues, puppet agent applying configs, problems oh my!
So I''m new to puppet and I''m having a bear of a time just getting a test server going. I installed puppet and the puppet client via yum on CentOS on AWS, so that saved me some time. I followed a few various blog posts about getting everything set up and applying a file, etc. Now I am trying to install a module (puppetlabs/apache) and it''s failing miserably for me. I
2009 Jul 01
10
Forcing puppetd ask puppemasterd for new changes
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
2012 Aug 17
8
puppet kick not working against windows service
I am running puppet 2.7.14 - CentOS 6 server, CentOS and windows 2008 R2 clients. I''m having problems with the "puppet kick" command - it works on linux clients, and on my windows box when "puppet agent --no-daemonize --verbose" is run from a command prompt. However, when I run it as a windows service, I get "Host blah failed: Connection refused -
2011 Jun 23
12
Turn off client autoupdate
Hello! By default puppet node connects to server periodically and looks if there is something execute. I''m wondering is it possible to make puppet clients not connect to server themselves? So that it would be possible to update a node only with puppetrun nodename. --- WBR, Sergey -- You received this message because you are subscribed to the Google Groups "Puppet Users"
2009 Dec 14
4
Provider Augeas not functional on Sles10?
Hi, I have a problem with augeas, puppet and Suse 10 SP2. Augeas works when I use the augtool to edit files. But I would like to use it in combination with puppet. My class looks something like this: augeas {"sysctl.conf": provider => "augeas", context => "/files/etc/sysctl.conf", changes => [ "set
2012 May 25
1
err: Invalid argument - /var/lib/puppet/state/puppetdlock
I have the error err: Invalid argument - /var/lib/puppet/state/ puppetdlock appearing on one of my servers. I have plenty of disk and plenty of inodes. The daemon is not running. I run it manually using /usr/sbin/puppetd --verbose --no-daemonize --onetime --server=xxx --fqdn=yyy There is no file /var/lib/puppet/state/puppetdlock and there is a root writable directory /var/lib/puppet/state
2010 Apr 21
12
puppetd stops
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
2012 Jul 31
2
Bad exit code?
Hi all, I''m running puppet agent as a onetime process. I would expect, if it can''t create the pid file, that it would exit non-zero. However, it seems to exit zero. Is there any way to change this? I''d like to know if it couldn''t run, and it seems that this is an error. [root@db1r1 ~]# puppet agent --onetime --detailed-exitcodes [root@db1r1 ~]# puppet
2011 Nov 01
2
Custom fact not set with mc-puppetd
Hello, I''ve mcollective 1.2.1 with puppet 2.6.12 on rhel5.6, facter 1.6.2 setup from http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML. Now I''ve create a custom fact in /usr/lib/ruby/site_ruby/1.8/facter/ customer_status.rb. On the client; Running facter customer_status works. Running ''puppet agent --test'' works, customer_status
2011 Jun 22
2
environment ENC vs cmdline
Hi all, I am using puppet with an ENC script. In this scripts YAML output the environment (generally "production") is set. For testing purposes I would like to start puppet runs from the cmdline of a managed host like: $ puppet agent --onetime --no-daemonize --verbose --no-splay --environment development The problem is the --environment Parameter is not being used if an environment