[Puppet Users] Error message : Could not configure routes from /etc/puppet/routes.yaml: Could not find terminus puppetdb for indirection facts

2015-02-02 Thread David Logan
Hi Folks, I've been searching for a solution for this and found one on here. Tried to run this (see output below) but am still getting the message in /var/log/messages (as in subject line). As you can see, the solution was to build it itself and then install, this was done successfully. Puppet

Re: [Puppet Users] Puppet EPEL RHEL5/6 vs RHEL7 (2.7.25 master with 3.6.2 clients)

2015-02-02 Thread Ugo Bellavance
> > Hi Ugo, > > The master must be upgraded before the agents or in other words, the > agents cannot have newer versions than the master. > > That is odd because it is actually working. I know it is not supposed to. > The easiest and most reliable path forward is to use yum.puppetlabs.com

[Puppet Users] user partitions fact in template

2015-02-02 Thread Tim Dunphy
Hey guys, I was thinking about turning my nrpe.cfg file into a template. So that I could customize lines like the following: command[check_root]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /dev/*vda* I would need to use just the name of the partition out of the following list: parti

[Puppet Users] Announce: Native Facter (cfacter) 0.3.0 is available!

2015-02-02 Thread Peter Huene
Native Facter (cfacter) 0.3.0 is a features-and-fixes release in the Native Facter pre-1.0 series. Included in this release is support for building Native Facter on Windows and Solaris. The EC2 and GCE facts were also implemented in this release. Notable updates: - Windows is now a supported

Re: [Puppet Users] Re: puppet cron help

2015-02-02 Thread Tim Dunphy
Hey Joey & Christian, Just like you would when manually adding a cronjob you should have '*/30', so your resource should look like this. cron { "facts-cron": command => "/usr/bin/facter -y > /etc/mcollective/facts.yaml", user=> 'root', hour=> 0, minute => '*/30' } Hope this helps!

[Puppet Users] Re: puppet cron help

2015-02-02 Thread Joseph Karns
Hello Tim: Just like you would when manually adding a cronjob you should have '*/30', so your resource should look like this. cron { "facts-cron": command => "/usr/bin/facter -y > /etc/mcollective/facts.yaml", user=> 'root', hour=> 0, minute => '*/30' } Hope this helps! Joey

Re: [Puppet Users] puppet cron help

2015-02-02 Thread Cristian Falcas
https://docs.puppetlabs.com/references/latest/type.html#cron cron { logrotate: command => "/usr/sbin/logrotate", user=> root, hour=> ['2-4'], minute => '*/10' } On Tue, Feb 3, 2015 at 12:55 AM, Tim Dunphy wrote: > Hey all, > > I'm attempting to setup a cron job via the cron res

[Puppet Users] puppet cron help

2015-02-02 Thread Tim Dunphy
Hey all, I'm attempting to setup a cron job via the cron resource in puppet. This is what I'm trying to express via puppet: */30 * * * * /usr/bin/facter -y > /etc/mcollective/facts.yaml This is what I've tried: cron { "facts-cron": command => "/usr/bin/facter -y > /etc/mcollective/f

[Puppet Users] puppetserver and LDAP terminus

2015-02-02 Thread Steve Huston
I'm in the process of testing the upgrade of our puppet 3.7.4 instance running under Apache/passenger to a new puppetserver setup on a RHEL7 machine. So far things have gone well, but the server is unable to do LDAP lookups. After spinning my wheels for quite some time wondering why I kept gettin

Re: [Puppet Users] Announce: Puppet Language Style Guide 2.0

2015-02-02 Thread Trevor Vaughan
Sorry for the double post but, in terms of validation, it would certainly have to come prior to other functions running so it probably does need to come first. I'll stand by my comment of needing some consistent method for determining where the interesting parts actually happen as a community. Th

Re: [Puppet Users] Announce: Puppet Language Style Guide 2.0

2015-02-02 Thread Trevor Vaughan
Inline On Mon, Feb 2, 2015 at 3:24 PM, Garrett Honeycutt wrote: > Awesome work on the new style guide! > Completely agree! > > == Section 5 > Why the arbitrary line length? Puppet's DSL does not have the ability to > break lines, such as '\' in bash, so imposing any limit does not buy >

[Puppet Users] Re: Pip provider fails on RedHat osfamily when pip not installed via RPM (Could not locate the pip command)

2015-02-02 Thread Dafydd James
Thank you! This really helped. sudo ln -s /usr/bin/pip /usr/bin/python-pip Or in puppet format: file { '/usr/bin/pip-python': ensure => link, target => '/usr/bin/pip', require => Package['python-pip'] } -- You received this message because you are subscribed t

Re: [Puppet Users] Unreported Windows nodes (Puppet 3.7.3, Exchange 2010)

2015-02-02 Thread Rob Reynolds
On Mon, Feb 2, 2015 at 5:05 AM, cko wrote: > I just noticed that the affected agents do not update the files located in > "C:\ProgramData\PuppetLabs\puppet\var\state". > > Also interesting: The "agent_catalog_run.lock" file is not properly > removed after a puppet run. > > See the timestamps on t

Re: [Puppet Users] Announce: Puppet Language Style Guide 2.0

2015-02-02 Thread Garrett Honeycutt
On 2/2/15 1:21 PM, Lauren Rother wrote: > The Modules team and I are excited to finally announce the newest > version of the Puppet Language Style Guide. > > We've reworked the guide to reflect the new features and capabilities of > Puppet 3.7, and we've expanded it to cover more topics related to

[Puppet Users] strange behaviour of custom package provider

2015-02-02 Thread sébastien dagnicourt
Found the error, was using a different value for ensure and it was not handled by my install method -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users

[Puppet Users] Announce: Puppet Language Style Guide 2.0

2015-02-02 Thread Lauren Rother
The Modules team and I are excited to finally announce the newest version of the Puppet Language Style Guide. We've reworked the guide to reflect the new features and capabilities of Puppet 3.7, and we've expanded it to cover more topics related to building manifests and modules. If you're interes

Re: [Puppet Users] Puppet array merge failure?

2015-02-02 Thread leam hall
Hey John, thanks! To add to your points, I'm referencing https://docs.puppetlabs.com/hiera/1/lookup_types.html#array-merge Your recommended Hiera command works fine on the master. Thanks! All NTP servers show up. However, they are not getting put into the ntp.conf file. I've modified both the sa

Re: [Puppet Users] puppet cloud provisioner - without enterprise -Error: Unknown Puppet subcommand 'node_aws'

2015-02-02 Thread Helen Paterson
I manage to get the puppet cloud provisioner working for AWS by: 1. Using ubuntu 14 2. Down loading the module from the forge https://forge.puppetlabs.com/puppetlabs/cloud_provisioner 3. creating the fog file https://docs.puppetlabs.com/pe/latest/cloudprovisioner_configuring.htm

[Puppet Users] strange behaviour of custom package provider

2015-02-02 Thread sébastien dagnicourt
I wrote a custom package provider in order to install remotely tar files (a bit like yum with rpm files). When testing I used it on a simple class file with one resource package like this : package {"testpackage": ensure => present, provider => myprovider, } It worked. When I use

Re: [Puppet Users] Puppet array merge failure?

2015-02-02 Thread jcbollinger
On Friday, January 30, 2015 at 11:33:37 AM UTC-6, leam hall wrote: > > > On Friday, January 30, 2015 at 12:11:20 PM UTC-5, Matthew Burgess wrote: >> >> >> On 30 Jan 2015 14:09, "leam hall" wrote: >> > >> > :merge_behavior: deep >> >> See >> https://docs.puppetlabs.com/hiera/1/lookup_types.html#

Re: [Puppet Users] puppet cloud provisioner - without enterprise -Error: Unknown Puppet subcommand 'node_aws'

2015-02-02 Thread Helen Paterson
Hi, I upgrade to ubuntu 14 to resolve the ruby error and then managed to install fog , but i still cannot connect to AWS Error: Could not autoload puppet/face/node_aws/create: cannot load such file -- fog Error: Could not parse application options: Could not autoload puppet/face/node_aws/creat

Re: [Puppet Users] Re: File 'replace => false' doesn't match my expectations...

2015-02-02 Thread Marc
You cannot specify source when using checksum 'none' Marc On Monday, February 2, 2015 at 12:35:31 PM UTC+1, Thomas Müller wrote: > > > > Am Dienstag, 20. Januar 2015 20:28:33 UTC+1 schrieb Marc: >> >> Using 'replace => false' should not trigger a checksum operation but >> given the time it takes

Re: [Puppet Users] Re: File 'replace => false' doesn't match my expectations...

2015-02-02 Thread Thomas Müller
Am Dienstag, 20. Januar 2015 20:28:33 UTC+1 schrieb Marc: > > Using 'replace => false' should not trigger a checksum operation but given > the time it takes with big files I think it does. > Does it make sense to perform checksum when 'replace' is set to false? > what about setting "checksum =>

Re: [Puppet Users] Unreported Windows nodes (Puppet 3.7.3, Exchange 2010)

2015-02-02 Thread cko
I just noticed that the affected agents do not update the files located in "C:\ProgramData\PuppetLabs\puppet\var\state". Also interesting: The "agent_catalog_run.lock" file is not properly removed after a puppet run. See the timestamps on the files ( http://i.imgur.com/qE87OB5.png ) On Monda