Set SSL ciphers for the Active MQ broker in Puppet Enterprise 2018.1
Improve MCollective stability by removing unneeded logrotate configuration in Puppet Enterprise
Tune ActiveMQ logging for large node populations in Puppet Enterprise
Disable the scheduled "refresh-mcollective-metadata" task on agent nodes in Puppet Enterprise
Change the MCollective password in Puppet Enterprise 2015.x to 2017.2.x
Tune ActiveMQ timeouts to improve MCollective connection reliability in Puppet Enterprise 3.7.2 to 2016.4.5 and 2016.5.x to 2017.2.1
ActiveMQ becomes unresponsive in Puppet Enterprise 2016.4.3 and earlier, 2016.5, and 2017.1
My agent node is not responding to "mco ping" in Puppet Enterprise 2016.1 to 2017.2
Resolve MCollective error messages about files in /var/lib/peadmin/.mcollective.d/ in Puppet Enterprise 2016.x to 2017.2.x
Keep MCollective facts updated on Windows for Puppet Enterprise 2016.2.x

See more

Set SSL ciphers for the Active MQ broker in Puppet Enterprise 2018.1

Patrick Grant

May 18, 2020 22:53
Updated

Did this solve your problem?

1 out of 1 found this helpful

If MCollective is enabled in 2018.1, port 61613 might be vulnerable depending on which cipher suites are in use. If you are no longer using MCollective, the simplest way to fix this issue is to rem...

Read this full article with Puppet Support

Sign in to your account Learn more about Puppet products

Can't sign in? Get help

Comments

0 comments

Please sign in to leave a comment.