similar to: apt-get lock the administration directory

I came in this morning to find all the servers all locked up solid: # passenger-status ----------- General information ----------- max = 20 count = 20 active = 20 inactive = 0 Waiting on global queue: 236 ----------- Domains ----------- /etc/puppet/rack: PID: 2720 Sessions: 1 Processed: 939 Uptime: 9h 22m 18s PID: 1615 Sessions: 1 Processed: 947 Uptime: 9h 23m

So I got dashboard up and running on our production system on Thursday before I left. Within 48 hours it had completed filled the /var filesystem. The ibdata1 file is currently at 8GB in size. 1. What size should I expect for ~500 nodes reporting every 30 minutes? 2. Are there some database cleanup scripts which I have managed to overlook that need to be run? -- Jo Rhett Net Consonance :

I''m seeing a recurring, nightly copy of files which are not changing. I get the following message every night from tagmail. 1. It happens once per day (not every 30 minutes) 2. The files haven''t changed in months 3. The files aren''t changing -- there''s only one md5 in the clientbucket for each file 4. There''s no schedule on the resource 5. The files

Hi, Does this still apply in puppet 3.0.2 in the puppet.conf file on the puppet master? [puppetmasterd] ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY If yes, is puppetmasterd correct or should it be something else, like [main] or [master]? Cheers, Oli -- You received this message because you are subscribed to the Google Groups "Puppet

Hello everyone... I have configured the puppetmaster to use Apache/Passenger. However, executing a configprint (puppet --configprint all) from either the puppetmaster or an agent shows servertype = Webbrick Has anyone else seen this? What do I need to do to correct this? Thanks! JA -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.

Actually, doing what logrotate suggests causes other problems. We don't have this problem on any other system so I am keen to understand the root of the issue rather than start messing around with the default permissions of the log directories. logrotate only matches /var/log/nginx/*log - /var/log/nginx/access.log & /var/log/nginx/error.log On the server where we have problems we have

Hi, I’m managing several machines with a 2.7.6 master, and 2.7.1 and 2.7.6 mixed, not yet all fully upgraded clients. On the puppet master, I want to kick a node but it exits with error code 3, which doesn’t seem right. The agent seems to return the wrong message. <hidden>:~$ puppet kick <hidden> --trace --debug --foreground Triggering <hidden> Getting status status is running

Hi Guys, I am a new puppet user and wanted some type of monitoring for puppet so deployed puppet-dashboard. It has been working very well for a few days not, but all of a sudden I start getting pending tasks and they never finish even after restarting all processes. They keep accumulating and never seem to finish even though the clients are running fine. I have the puppet-dashboard

Greetings, I have a tested, working setup of Puppet and Webrick. I can add nodes, classes, etc. Then I switched to Puppet/Passenger and get the error below. Puppet, Apache and Passenger are all up. I have installed using *YUM *repos and *GEMs*. So, I have the most updated packages they have. Puppet version: 2.7.19 Ruby version: 1.8.7 (2011-06-30 patchlevel 352 i386) Apache: 2.2.15 The error

It?s interesting in your world, where ?broken? is ?functions exactly as it is documented to work? If you want it to match subdirectories then you should add to the logrotate, or add another one yourself for each subdirectory. It?s not hard, and it?s certainly not broken. It does what you tell it to do. On Sep 24, 2015, at 6:33 AM, Andrew Holway <andrew.holway at gmail.com> wrote: > Hmm,

somefile.pp class mumble { } class mumble::testcontents inherits mumble { file { "/tmp/testfile": path => "/tmp/testfile, ensure => present, mode => 0640, content => "I am a test file.", puppet parser validate passed it. puppet apply says it is run yet no /tmp/testfile appears the puppet master is running and this is being

I''m looking to use an external node classifier (ENC) in our environment. What''s the easiest way to programmatically get currently applied classes (and class parameters) for all hosts, with the goal of dumping it into a database for later retrieval by the ENC script? Nodes are currently classified via site.pp. thanks -- You received this message because you are subscribed

Hi Y'all, We have nginx set up and we are having problems with logrotate. The permissions and users do not seem to be any different from other machines that are working ok however the /var/log/nginx does have a directory in there that we are using to collect some special log stuff. Could this subdirectory be interfering with the logrotate process? ta Andrew [root@ ~]# logrotate -d

Is there any chance we could get a PV AMI for CentOS 7 to match the HVM version at https://aws.amazon.com/marketplace/pp/B00O7WM7QW/ref=srh_res_product_title?ie=UTF8&sr=0-2&qid=1442957668341 We have prepurchased reserved instances based on older PV machines (m1, c1, etc) It would be very very helpful to have a PV AMI so we could migrate to CentOS 7 on those image types.

Hi, My puppetmaster is running through apache, and now I am setting up dashboard to be run by apache too. I followed docs in http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#starting-and-managing-delayed-job-workers, but after I restarted httpd, I see a apache welcome page. I set documentroot to be: DocumentRoot /usr/share/puppet-dashboard/public/

Hey guys, Relatively new to Puppet and I''m trying to setup tagmail to send all emails to me: at one point I''ll filter that down to errors and whatnot (based on tags) but for now I just want to get it working. Master Puppet server is setup with Passengers, all works well: /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is

Hi, When I execute *puppet agent --test --debug --verbose* on the target host, I receive the following error message: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class pe_accounts for targethost on node targethost warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run I enabled debugging for the Puppet Master, and

On Sep 23, 2015, at 9:03 AM, Karanbir Singh <mail-lists at karan.org> wrote: > On 22/09/15 22:37, Jo Rhett wrote: >> Is there any chance we could get a PV AMI for CentOS 7 to match the HVM version at https://aws.amazon.com/marketplace/pp/B00O7WM7QW/ref=srh_res_product_title?ie=UTF8&sr=0-2&qid=1442957668341 >> >> We have prepurchased reserved instances based on

Hey Guys, So i have puppetmaster running and well. I have a few questions 1) Even though i followed instructions on http://projects.puppetlabs.com/projects/1/wiki/Using_Mongrel on using Mongrel, puppetmaster is probably still using webrick since the client connection timeout still occurs. How do i make it use mongrel? 2) Now after messing a little with /etc/sysconfig/puppetmaster i increased

Hey all, I have a question regarding the choice to move to spaces (rather than tabs) in the editor. May I ask the reasoning behind this? Furthermore, is there a way to revert to the ''old style'' that used tabs instead? I prefer this, as it makes the code look cleaner. -- You received this message because you are subscribed to the Google Groups "Puppet Users"