Ask Your Question
0

Puppet PE 2015.2 Status Acknowledgement

asked 2015-08-03 06:10:55 -0500

FranzCC gravatar image

Hi again,
Installing the new puppet agent reflects changes in the status overview.
This is clar to me, but why the status remains changed ?
It's mcollective which remains on status changed.
How i can tell puppet PE that the status is normal, and no one did change /etc/default/mcollective.
Details:
Property: enable
Old Value: false
New Value: true
Message: enable changed 'false' to 'true'
Class: Puppet_enterprise::Mcollective::Service

Perhaps anyone can provide a solution how to ack the state to "normal".

Rgds.

Franz

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
0

answered 2015-08-06 23:09:38 -0500

GregLarkin gravatar image

Are you saying that every time the agent runs, the mcollective service is attempted to be started? If that's the case, then check the /var/log/puppetlabs/mcollective*log files to see if there's a message indicating what the problem could be.

edit flag offensive delete link more
0

answered 2015-08-07 02:10:03 -0500

FranzCC gravatar image

Hi Greg, thanks for the hint. I checked the log, and there were SSL errors for mcollective. So i removed the files in /etc/puppetlabs/mcollective/ssl and did a puppet agent -t. No errors have been logged since then, but the change remains. Aug 7 09:08:06 host01 puppet-agent[18966]: (/Stage[main]/Puppet_enterprise::Mcollective::Service/Service[mcollective]/enable) enable changed 'false' to 'true' Every time the agent runs (via cron) this line shows up in the syslog. How can i tell puppet that there was no change ?

Rgds.

Franz

edit flag offensive delete link more

Comments

The only way you can "tell" Puppet not to continually attempt to start the service is by making sure that the process is running. If the service keeps failing, that need to be fixed, and once it is, Puppet will stop attempting to start it. What does the command "service mcollective status" say?

GregLarkin gravatar imageGregLarkin ( 2015-08-07 14:00:40 -0500 )edit

Also post a link to a pastebin of the errors in the log file if they reappear. If the status command reports that the service is not running, run this command and post a link to a pastebin of the output: "sh -x /etc/rc.d/init.d/mcollective start"

GregLarkin gravatar imageGregLarkin ( 2015-08-07 14:02:36 -0500 )edit

Hi Greg, sorry for the delay. The service starts as expected, but that doesn't change anything. Is there any tracing function available ? Rgds. Franz

FranzCC gravatar imageFranzCC ( 2015-08-13 01:08:10 -0500 )edit

I would run "puppet agent -t --debug" and capture all of the output. There should be a point where you see a command that Puppet issues to check the status of the service. We need to figure out why that returns "not running" if it is actually running. Please post a link to a pastebin of the output.

GregLarkin gravatar imageGregLarkin ( 2015-08-13 11:17:15 -0500 )edit

Posted only relevant data ! First run (i reinstalled the puppet agent, and deleted all files belonging to): http://pastebin.com/ZYMgTkj9 Second run: http://pastebin.com/cH7KBkP3 So, puppet agent doesn't check, that the service is running, loaded and active. Seems to be a BUG. Rgds. Franz

FranzCC gravatar imageFranzCC ( 2015-08-14 06:46:23 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2015-08-03 06:10:55 -0500

Seen: 88 times

Last updated: Aug 07 '15