Cron[pe-mcollective-metadata] automatically run and made few changes unexpectedly to my clients. This change have made few replacement on
From the /var/log/messages file on one of the machines:
Jan 14 12:30:01 vm12 /usr/sbin/cron: (root) CMD (/opt/puppet/sbin/refresh-mcollective-metadata) Jan 14 12:33:53 vm12 puppet-agent: (at /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/type/package.rb:430:in `block (3 levels) in <module:Puppet>') Jan 14 12:33:54 vm12 crontab: (marshal) LIST (marshal) Jan 14 12:33:54 vm12 puppet-agent: (/Stage[main]/Puppet_enterprise::Mcollective::Server::Facter/Cron[pe-mcollective-metadata]/ensure) created Jan 14 12:33:54 vm12 crontab: (marshal) REPLACE (marshal) Jan 14 12:33:54 vm12 puppet-agent: Finished catalog run in 1.31 seconds
More information :
It is NIS related. IT has public NIS accounts with UID 0 - for root access on IT servers. Some of our machines think that all system files are (improperly) owned by the user accounts... (so we do a ls -la under /, a bunch of files owned by someone other than root. ). These UID 0 accounts have been around for a long time... it is very strange that the problem is showing since this run.