Puppet Community

Ah, this page with “puppet-agent component version numbers”

<https://puppet.com/docs/puppet/5.5/about_agent.html#puppet-agent-component-version-numbers>

<@U2S1MUUQ7> Ah, here you go: <https://puppet.com/docs/puppet/6/platform_lifecycle.html#puppet-agent-components>

hah…woops. Even that table is wrong.
It lists `puppet` version 6.27.1 in `puppet-agent` 6.27.1

Just found the <https://tickets.puppetlabs.com/browse/PUP-11432>

Hi community. Not sure if I have a Q/A question - is there any advice available for using --logdest &lt;file&gt; with 'puppet catalog compile'? I'm not seeing it produce any output in any file provided, and it ignores /dev/null

e.g $ puppet catalog compile --log_level debug --logdest /tmp/log.txt --confdir /tmp/puppet_ctl | head # all of the output goes to stdout, none to /tmp/log.txt. Maybe it's unique to 'puppet catalog compile' (?)

I've figured out how to use `--log-level warn` but if it produced any warning output, that could break anything expecting json on input, lol. I was hoping to  be able send to the log output to a temporary file computed at runtime

fwiw testing out a masterless config, after Alessandro Franceschi's book Extending Puppet (Packt). It might have been published circa Puppet 4 but afaict is the book to go to lol

This is with Puppet 7 from FreeBSD ports i.f, running under a Bhyve VM. Looking forward to installing it under OpenSUSE, testing first lol

When one uses Puppet's _*pe_patch*_ class is there anyway to disable all patch schedules temporarily due to  e.g, a service window when you don't want to "rock the boat" by patching?

Any puppet on windows users here who could contribute factsets for facter 4 to <https://github.com/voxpupuli/facterdb>?

is it just me or did this stop working: <https://puppetlabs.github.io/>

That domain is available for purchase from <http://www.nic.io/>

<http://github.io|github.io>, though, seems to be fine.

Hi Sam,

Theres a blog post about the CEM modules here but I believe it should just be run from the PE console

Which OS version is Puppet Server running on?

<@U11MDJNGZ> CentOS 7 (it will become Ubuntu at some point)
puppetserver-7.6.1-1.el7.noarch

Ah, using RedHat 8 or Ubuntu 16.04+ will probably fix it.

This error can occur when launching an external process if the process forks `java`. There can be enough copy-on-write allocation due to thread activity between `fork()` and `exec()` that Linux can run out of memory.

`Open3` tries to avoid this by using `posix_spawn()`, which is explicitly designed to avoid copy-on-write, but  GLIBC ended up using `fork()` to implement that system call and canceled out the benefits. That was fixed after RedHat 7:

<https://sourceware.org/bugzilla/show_bug.cgi?id=10354>

The `Puppet::Util::Execution` library also avoids this by ensuring `vfork()` is used.

yes, `Puppet::Util::Execution` ... I was trying to recall the name. I ended up using a gem called `uuidtools` , but I had to install the gem, reload the puppetserver

That'd likely be a good function for puppetlabs/stdlib or voxpupuli/extlib

See the `puppetlabs-stdlib` module at <https://forge.puppet.com/puppetlabs/stdlib?src=slack&amp;channel=puppet>

<@U01HHDKT8BY> chimes in every time :slightly_smiling_face:

in the end it was easy with uuidtools, but I had to install a gem and restart the puppet server

ok, I'm gonna install the gem `uuidtools`, and I give up using `open3` ... I'm sure it's gonna work

I raised <https://tickets.puppetlabs.com/browse/FACT-3114>

<@U1PC2RAH0> I ran it right a few minutes ago and it worked for me on Ubuntu and CentOS. And I have facter 4.2.8