@Yorokobi THANKS!! YOU THE MAN! Remind me to buy you a beer sometime... 🙂

TWO nodes now. FTW!

now to see if I can repeat what I just did for a fresh clean install. LOL

Hello folks, I ran puppet parser validate successfully on a file but when I tested the code, I received a puppet-lint error

WARNING: optional parameter listed before required parameter on line 1

This is what's failing.

class foo (
  $an_optional_param = 'foo',
  $a_required_param,
) {

It should look like this, with the required parameter first:

class foo (
  $a_required_param,
  $an_optional_param = 'foo',
) {

This is what's failing.

class foo (
  $an_optional_param = 'foo',
  $a_required_param,
) {

It should look like this, with the required parameter first:

class foo (
  $a_required_param,
  $an_optional_param = foo',
) {

This is what's failing.

class foo (
  $an_optional_param = 'foo',
  $a_required_param,
) {

It should look like this, with the required parameter first:

class foo (
  $a_required_param,
  $an_optional_param = 'foo',
) {

puppet parser validate - syntax correctness

puppet-lint - opinionated rules how that code should look like

opinions <3

This message was deleted.

This message was deleted.

I shutdown a puppet client node to test puppetDB (there's two clients and my server for a total of 3 nodes) Why after a couple hours does puppetDB still show 3? I have the clients set to check in hourly. Any thoughts?

one of the ttls

grep ttl /etc/puppetlabs/puppetdb/conf.d/database.ini

scratch that, ttl will remove them from puppetdb due to inactivity

Why did you expect it to change though? 3 seems valid

you can check node status

puppet node status certname

it should say when was last report and last facts

I am not quite sure what time makes it 'inactive' though

3 is valid - until I shut one client node down, 3 hours ago. I expect it to show 2 active and 1 inactive

any I wonder why this doesn't work - both clients have signed certs puppet node status pupcli_two Error: Could not retrieve status for pupcli_two: Failed to find '/pdb/query/v4/nodes/pupcli_two' on any of the following 'server_urls': https://puppet.lan:8081

I think it has something to do with the fact I have to use 'localhost' with my curl queries

I plan on fixing that, but that's how it is now

This message was deleted.

We have two puppet masters, and several servers running passenger. Generally the clients connect to the passenger hosts. We’re moving some clients around and changing their IP addresses - we have a simple module which updates the /etc/hosts file with the IP / FQDN of the host (using $::ipaddress) … Seemingly randomly the code uses the old IP address of the server. Checking facter on the client it reports ipaddress correctly. The yaml file for the host on the passenger servers shows the old IP for some passengers and new on others … Removing the yaml files does not improve the situation … Any ideas ? I assume its some sort of caching in the puppet masters / passenger servers but we dont know how to clear it (and its not practical to reboot the passenger servers for each host move - and we dont know if that would work anyway). Any suggestions ?

According to the doc https://www.puppet.com/docs/puppetdb/7/pdb_client_tools.html PDB client tools are available for 'puppet enterprise' - yet I can see them freely available for download. Can a opensource/community puppetserver use these, or would this be in violation of licensing, etc?

I think they are useless in OSS environment. they use specialized API