similar to: bug: recursive directory copy that re-copies nightly

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 :

Hello CentOS users, I have problems posting the question below to the Nagios mailing list (my subscription is not accepted for some reason). Has anybody of you already had this probably frequent problem with Nagios in CentOS? I can''t use check_squid from command-plugins.cfg (s. below) Thank you for any hints Alex ---------- Forwarded message ---------- To: nagios-users at

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

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,

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

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

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

I'm looking to troubleshoot this error when I run "tail /etc/httpd/logs/error_log" [Tue Oct 09 07:22:59 2007] [error] [client 127.0.0.1] Directory index forbidden by rule: /var/www/html/ (I get this when I run Nagios' "./check_http -H 127.0.0.1".) All I did was install CentOS and then modify httpd.conf to include "ServerName 192.168.1.10:80" and also

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.

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 to everyone, I have a doubt about how puppet works and I would appreciate if some of you have the answer to this. The question arise in the following scenario: Suppose I have two module that both of them need to install a package. Let''s say I have a module that install apache and another that installs mysql. They have something like this at some point: apache::install class

Folks- Just wanted to plug a totally awesome software package from a group I know: UDR (UDT Enabled Rsync). For those not familiar with UDT, it is a low level network protocol based on UDP that allows for high speed transfers over high latency WAN networks: http://udt.sourceforge.net/ For a while the UDT API was available, developed by the Laboratory for Advanced Computing at the

1. The UDT library is a BSD-licensed accelerated UDP-based transport. Would tinc be able to use this for UDP-based connections and would the licensing be acceptable? http://udt.sourceforge.net/index.html 2. I would like to see a 3rd compression protocol added to tinc: one based on the Mahoney compression schemes would be worth investigating (need something fast and uses small RAM on

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

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