How do I tell what ran puppet on my system?

asked 2018-03-22 17:08:41 -0500

updated 2018-03-23 09:10:08 -0500

DarylW gravatar image

I'm trying to set up monitoring for a database server, but found my config changes being wiped out. I know we use puppet in our environment, so I disabled it on the machine while I tinkered so I could figure out what setting I needed, using:

mco service puppet stop -F hostname=bonnie

I then started working again, only to find my changes once more wiped out, so I checked to see if it was still off, and it sure seems to be:

[root@bonnie lib]# service puppet status
Redirecting to /bin/systemctl status  puppet.service
● puppet.service - Puppet agent
   Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Thu 2018-03-22 16:25:13 EDT; 1h 40min ago
 Main PID: 963 (code=exited, status=0/SUCCESS)

Mar 22 15:41:35 bonnie.stockpile.nemgint.com puppet-agent[963]: Setting 'pluginsync' is deprecated.
Mar 22 15:41:35 bonnie.stockpile.nemgint.com puppet-agent[963]:    (at /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/defaults.rb:1744:in `block in <module:Puppet>')
Mar 22 15:41:50 bonnie.stockpile.nemgint.com puppet-agent[963]: Config file /etc/puppetlabs/puppet/puppet.conf changed; triggering re-parse of all config files.
Mar 22 16:01:16 bonnie.stockpile.nemgint.com puppet-agent[963]: Skipping run of Puppet configuration client; administratively disabled (Reason: 'reason not specified');
Mar 22 16:01:16 bonnie.stockpile.nemgint.com puppet-agent[963]: Use 'puppet agent --enable' to re-enable.
Mar 22 16:04:05 bonnie.stockpile.nemgint.com puppet-agent[963]: Config file /etc/puppetlabs/puppet/puppet.conf changed; triggering re-parse of all config files.
Mar 22 16:04:20 bonnie.stockpile.nemgint.com puppet-agent[963]: Config file /etc/puppetlabs/puppet/puppet.conf changed; triggering re-parse of all config files.
Mar 22 16:25:12 bonnie.stockpile.nemgint.com systemd[1]: Stopping Puppet agent...
Mar 22 16:25:12 bonnie.stockpile.nemgint.com puppet-agent[963]: Caught TERM; exiting
Mar 22 16:25:13 bonnie.stockpile.nemgint.com systemd[1]: Stopped Puppet agent.
[root@bonnie lib]#  puppet agent --test
Notice: Skipping run of Puppet configuration client; administratively disabled (Reason: 'reason not specified');
Use 'puppet agent --enable' to re-enable.

...so I'm a little baffled as to how these changes are being made; am I wrong about puppet being off? Is there some way to see what is running puppet on this system?

edit retag flag offensive close merge delete

Comments

If you want to force puppet not to run, you can set it to `--disable` (followed by an optional message) - https://puppet.com/docs/pe/2017.3/managing_mcollective/controlling_puppet.html#ariaid-title4 it will still attempt to run, but give you your last 'administratively disabled' message from the ..

DarylW gravatar imageDarylW ( 2018-03-23 09:12:44 -0500 )edit

.. end of your example. It shouldn't be making any configuration changes.

DarylW gravatar imageDarylW ( 2018-03-23 09:13:44 -0500 )edit

I did this: [root@bonnie ~]# puppet agent --disable [root@bonnie ~]# puppet agent --test Notice: Skipping run of Puppet configuration client; administratively disabled (Reason: 'reason not specified'); Use 'puppet agent --enable' to re-enable. Made my changes, and they were still reverted back.

pmbaldwin gravatar imagepmbaldwin ( 2018-03-23 11:42:58 -0500 )edit

Is there any way to tell what is running puppet on this system? Because it sure seems to be off locally, but config changes are definitely being reverted.

pmbaldwin gravatar imagepmbaldwin ( 2018-03-23 11:43:47 -0500 )edit