similar to: get a *structured* version of the puppet agent output

Hi, When I put noop = true in /etc/puppet/puppet.conf on the node in question, I observe no changes. Great. Good But also, I see because of report = true absolutely zero information in the yaml regarding what would have been changed. Is there an equivalent to the above for "test = true" or must I alter the rc file to include --test ? Thanks ahead Puppet wizards!!! -- You

Hey guys, I'm trying to rotate a logstash log that can grow pretty large. 3.4GB last I saw! And that's because the logrotate script I came up with didn't work. The error I get on a syntax check is this: #logrotate -f logstash size: '100M': No such file size: '100M': No such file size: '100M': No such file size: '100M': No such file size:

I asked a similar question about a year ago and didn't get any answers. So I thought I'd try again. What do people do to get their syslog messages on CentOS 7 into a remote ELK stack. I've tried lots of things involving rsyslog, filebeat, redis, logstash and so on in lots of different configurations but nothing really works. I can get rsyslog to talk directly to logstash (acting as

Hallo, I try to send my centos 7 logfiles to an logstsah server. Can anyone give me an hint how to fix this problem? Thanks Ralf > {"index"=>{"_index"=>"%{[@metadata][comline]}-%{[@metadata][version]}", > "_type"=>"doc", "_id"=>"U1XLXGkBpfl5FoHeY4J8", "status"=>400, >

Hi all, I am trying to use puppet (2.7.18) for downgrading varnish cache on Centos Linux (6.3). Unfortunately there are two varnish RPMs (which seem to have circular dependencies): varnish-3.0.4-1.el6.x86_64 varnish-libs-3.0.4-1.el6.x86_64 When using "ensure" for downgrading I get a bunch of errors: err: /Stage[main]/Varnish/Package[varnish-libs]/ensure: change from 3.0.4-1.el6

Hey all, I'm trying to do a find of all files with the phrase 'varnish' in the name, but want to exclude a user home directory called /usr/local/digitalplatform. Here's what I was able to come up with: find / -path '/usr/local/digitalplatform/*' -prune -o -name "*varnish*" Which results in this: [root at uszmpwsls014lb ~]# find / -path

Hi, I use a module (for Varnish in this case) which has the typical install, service, package classes. -- modules/varnish/manifests/install.pp: class varnish::install { package { $varnish::params::package_name: ensure => installed, } } -- modules/project/manifests/proxy.pp class project::proxy { include varnish } -- manifests/site.pp node proxy {

Hi Thomas, > What's really nice is, that it understands the Icecast log format > extension where we record the duration of the connection in seconds. I can't take credit for that, the work was done by Alejandro: https://github.com/piwik/piwik/pull/65 Cheers! Daniel

No problem installing open puppet and using it. patterns run aok. when trying to use the installer for pe, on the puppetmaster, installs ok. when trying to use the installer for pe, on the puppet agent, installs ok but no cert sent as shown by puppet cert list on puppetmaster. also puppet agent --test on puppet agent shows err: could not retrieve catalog from remote server: error 400 on

Hi All, I started a 501c3 (not-for-profit) organization back in February 2011 to deal with information archival. A long vision here, I wont bore you with the details (if you really want to know, e-mail me privately) but the gist is I need to build an infrastructure to accommodate about 2PB of data that is database stuff, stored video, crawl data, static data sets, etc. Right now in my testing of

Guys, I need to parse my dovecot log files with logstash grok patterns. Is there any document specifying the patterns used by dovecot to write it's logs? I need to find all the log possibilities that could be writed to log files by dovecot. So, if a document like that exists or if anyone could answer my question, I'll could make the parser with less difficult. -- Att. Bruno

My class reads like: class name1::name2 ($gidvariable) { file { "somepath-to-file": ensure => file, mode => ''0640'', gid => $gidvariable, } } The problem is that the file isn''t getting set to the $gidvariable''s value which is a string "abc". The other things work (presence as file, mode). Stuart -- You

Hi all, I''ve been looking at a potential problem, as documented here: http://projects.puppetlabs.com/issues/19241 To do with a leak within the KahaDB persistence layer of ActiveMQ. Specifically, there are reports of the db.data file growing unbounded: https://issues.apache.org/jira/browse/AMQ-3956 I''m hoping to find out information from other PuppetDB users to see if this is

Greetings, we are trying to setup puppetdb, nut our clients get the following error: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for lxa7t.unix.lan: Failed to submit ''replace facts'' command for lxa7t.unix.lan to PuppetDB at puppetdb:8081: Connection refused - connect(2) Info: Retrieving

Hello, I have configured puppet and puppetdb (storeconfig) with postgresql and the service run and the collecting are good for example: I can make query with the next command and responds ok . [.........................] [root@master]# curl -X GET -H ''Accept: application/json'' http://127.0.0.1:8080/v2/facts --data-urlencode ''query=["=", "name",

Puppet 3.3.1 // CentOS release 6.4 (Final) rpm -qa | grep puppet puppetlabs-release-6-7.noarch puppet-3.1.1-1.el6.noarch puppetdb-1.3.0-1.el6.noarch puppet-server-3.1.1-1.el6.noarch puppetdb-terminus-1.3.0-1.el6.noarch Installed from yum packages: Running Transaction Installing : puppetdb-1.3.0-1.el6.noarch

PuppetDB is operating fine, but I can''t figure out how to disable it from listening globally on TCP 1099 or 58722 How do I disable them from listening globally without having to resort to iptables? $ lsof -i -n -P | grep java | grep LISTEN java 30115 puppetdb 22u IPv6 119118 0t0 TCP *:1099 (LISTEN) java 30115 puppetdb 23u IPv6 117236 0t0 TCP *:58772

Hi, I am having problems installing Puppet Server. My gem list follows and then the attempt to install puppet-server. The specific errors are: Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs) Requires: ruby-augeas Error: Package: hiera-1.2.1-1.el6.noarch (puppetlabs) Requires: rubygem-json Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

I have a puppet master install which uses puppetdb. I also have puppet dashboard installed with the inventory service running. I want multiple puppet masters using a single puppetDB server. Puppetdb is installed on separate vm. How can I get the dashboard inventory to use the puppetdb server to get the inventory records? Where do I configure the dashboard inventory so it uses puppetdb? I

PuppetDB 1.1.0-rc4 is now available for download! This is a feature and bug-fix release candidate of PuppetDB. Note: Release candidates 1-3 were never pushed to repositories due issues in packaging that were discovered prior to release. RC-4 is the first packaged release candidate for PuppetDB 1.1.0. # Downloads ============== Available in native package format in the pre-release repositories