Re: [Puppet Users] PuppetDB Issue with large array-valued fact

On 04/19/2016 10:39 AM, Mike Sharpton wrote: Again,*_thank you_* very much. If I could buy you a beer, I would. The machines in question are a mix of RHEL5/6/7. Hah, you're very welcome. Thanks for confirming the OS; that means this isn't just a Solaris issue like that facter ticket suggest

Re: [Puppet Users] Hiera Error 400 on SERVER: Could not find data item classes in any Hiera data file and no default supplied

Unfortunately, I wrote agen1 when I edited my post not to show internal info. I tried your alternative solution (hiera_include('classes', [])) and it, well, allows the puppet command (puppet agent --noop --test --verbose by the way) to run OK instead of throwing a 400, but I don't see it applyi

[Puppet Users] Feedback on reporting verbose/debug/show_diff to syslog/eventlog (PUP-6125)

I'd like to solicit feedback on a ticket around changing some behavior in logging when using --verbose, --debug, --test, etc. PUP-6125 points out that --logdest states Where to send log messages. Choose between 'syslog' (the POSIX syslog service), '

Re: [Puppet Users] Hiera Error 400 on SERVER: Could not find data item classes in any Hiera data file and no default supplied

Ugo, In your last example you used 'agen1' instead of 'agent1'. Maybe it's just a typo? Those are the best problems :) I also don't see where the 400 error comes from, can you capture that somewhere? An alternative solution - or maybe complementary - is to change line 11 to say `hiera_include('cl

Re: [Puppet Users] Patterns for multi-arch libraries...

On 4/19/16 9:06 AM, J.T. Conklin wrote: Rob Nelson writes: Silly question, but what package manager doesn't let you upgrade those two packages independently but also doesn't update the dependent packages at the same time? We have this problem on CentOS machines using the yum provider. The log

Re: [Puppet Users] Strategies for "boring" packages

On 4/18/16 5:47 PM, J.T. Conklin wrote: At work, we've written about 120 modules in our puppet code repository. About two dozen are "interesting", in that they have lots of parameters and configuration that is specific to our environment. The balance are "boring", rather they are mostly boilerpl

Re: [Puppet Users] PuppetDB Issue with large array-valued fact

Wyatt, Thank you very much for your time and reply. I greatly appreciate it. I ran your query and your suspicions are correct. Some DB servers lead the pack with a massive amount of data due to all the disk that is there. We will probably just make these facts nil on all machines as we don'

[Puppet Users] Hiera Error 400 on SERVER: Could not find data item classes in any Hiera data file and no default supplied

Hi, I'm currently testing hiera and I can't make it work. I get this error: Error 400 on SERVER: Could not find data item classes in any Hiera data file and no default supplied at /etc/puppet/manifests/site.pp:11 on node. I'm trying to do something like this: https://docs.puppet.com/hiera/3.0

Re: [Puppet Users] Re: Puppet on windows ignoring puppet.conf

On Tue, Apr 19, 2016 at 7:56 AM, Mike Sharpton wrote: > Note sure if they changed the path with 1.4.1. The path used to be what > is below. May want to try that. > Just to confirm, we haven't changed the location of where puppet.conf goes. > > C:\programdata\PuppetLabs\puppet\etc > Yep that

Re: [Puppet Users] Patterns for multi-arch libraries...

That's weird, but I guess it kind of makes sense as they're independent. Shame they have conflicts, though. It looks like, of all things, it's the shared man pages causing the problem... https://bugs.centos.org/view.php?id=5489 I assume you have both versions on purpose, but in case that wasn't th

Re: [Puppet Users] Patterns for multi-arch libraries...

Rob Nelson writes: > Silly question, but what package manager doesn't let you upgrade those > two packages independently but also doesn't update the dependent > packages at the same time? We have this problem on CentOS machines using the yum provider. The logs reported something to the effect of

Re: [Puppet Users] PuppetDB Issue with large array-valued fact

Hey Mike, The unsatisfying answer is that PuppetDB handles giant facts (particularly array-valued facts) pretty badly right now, and facter's disks, partitions, and mountpoints facts can all get pretty huge in cases such as SANs and similar. Can you try and see if the bulk of those fact paths

Re: [Puppet Users] Strategies for "boring" packages

Luke Bigum writes: > In my mind the "purest" way would be to go individual modules for each > package/service combination. If the only requirement is that you are > handling the differences between Red Hat and Debian flavours, then a > module per package/service. These modules would be wholly self

[Puppet Users] Re: Puppet on windows ignoring puppet.conf

Note sure if they changed the path with 1.4.1. The path used to be what is below. May want to try that. C:\programdata\PuppetLabs\puppet\etc On Tuesday, April 19, 2016 at 9:38:20 AM UTC-5, Mattis Haase wrote: > > Hello, > > we have been using puppet for unix machines for quite a while and it w

[Puppet Users] PuppetDB Issue with large array-valued fact

Hello all, We are running Puppet 4.2.2 and PuppetDB 3.2.0 with around 2400 nodes and growing. I am noticing some bad behavior with our PuppetDB, which is only going to get worse if what is below is correct. I see the error below in the puppetdb log. * ERROR [p.p.mq-listener] [cfe52545-29f8-4

[Puppet Users] Puppet on windows ignoring puppet.conf

Hello, we have been using puppet for unix machines for quite a while and it works fine. I have installed the latest puppet-agent (1.4.1) on Windows Server 2012R2. The installation went fine and the communication between the puppetmaster and the client works. However, it uses the production en

Re: [Puppet Users] Puppetdb garbage collection failing

Hello Wyatt, I think I have ran into an issue with large structured facts. I posted a new message about it, but I was wondering if you have a solution for large partitions and disks facts? I am not sure what to do as I cannot disable facts, and I have a large number of nodes. Your help is a

Re: [Puppet Users] Strategies for "boring" packages

In my mind the "purest" way would be to go individual modules for each package/service combination. If the only requirement is that you are handling the differences between Red Hat and Debian flavours, then a module per package/service. These modules would be wholly self contained and rely on so