<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I’ve restored the serve to a prior snapshot<div class=""><br class=""></div><div class="">I had to run rudder agent reinit to get the nodes to show up and be accepted again</div><div class=""><br class=""></div><div class="">I am back to where I was before the wind blew </div><div class=""><br class=""></div><div class="">Awaiting suggestions</div><div class=""><br class=""></div><div class="">Al;</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 2, 2016, at 12:23 PM, Al Joslin <<a href="mailto:allen.joslin@gmail.com" class="">allen.joslin@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=windows-1252" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I threw caution to the wind and installed the revised <a href="http://servicesmanagement.st/" class="">servicesManagement.st</a></div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>I copied it from:</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="http://www.rudder-project.org/redmine/projects/rudder/repository/rudder-techniques/revisions/ea8dd328300427beacc91cc4d9ee84b27a642d5a/entry/techniques/systemSettings/process/servicesManagement/3.0/servicesManagement.st" class="">http://www.rudder-project.org/redmine/projects/rudder/repository/rudder-techniques/revisions/ea8dd328300427beacc91cc4d9ee84b27a642d5a/entry/techniques/systemSettings/process/servicesManagement/3.0/servicesManagement.st</a></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Into:</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>/opt/rudder/share/techniques/systemSettings/process/servicesManagement/3.0/<a href="http://servicesmanagement.st/" class="">servicesManagement.st</a></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>/var/rudder/configuration-repository/techniques/systemSettings/process/servicesManagement/3.0/<a href="http://servicesmanagement.st/" class="">servicesManagement.st</a></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>(committing the change to git [from within the 3.0 folder] in the latter case)</div><div class=""><br class=""></div><div class="">Rudder didn’t see that as a change so nothing was applied</div><div class=""><br class=""></div><div class="">The only way I know how to cause the rules to be applied is to change something, so I modified the lessThan&greaterThan instance values in the existing servicesManagement directive instance</div><div class=""><br class=""></div><div class="">The rules were then applied but the error was still there, so I figured that I would have to rebuild the directive to pick up the changes</div><div class=""><br class=""></div><div class="">So I deleted and rebuilt my directive instance, which caused the Rules to be applied as soon as the deletion was applied</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- I guess I should have disabled them to make changes?</div><div class=""><br class=""></div><div class="">Then I re-added the new instance of the serviceManagement directive to the rules - in their settings panes</div><div class=""><br class=""></div><div class="">But the [updated] directive (with the same name as the old one) wouldn't show up in the compliance view, even when I deleted all teh directives, saved and then re-added and saved…</div><div class=""><br class=""></div><div class="">So I rebuilt the Rule (again with the same name as the old one) — and then none of the directives would show up in compliance - even after 5mins of the wheel spinning around</div><div class=""><br class=""></div><div class="">So I restarted rudder - no effect: the compliance wheel is still spinning on the rebuilt rule and no directives are showing up in the lists below</div><div class=""><br class=""></div><div class="">So I rebooted the rudder machine - no effect: the compliance wheel is still spinning on the rebuilt rule and no directives are showing up in the lists below</div><div class=""><br class=""></div><div class="">OK, so I’m kinda wishing I’d waited for the release…</div><div class=""><br class=""></div><div class="">Suggestions? Options?</div><div class=""><br class=""></div><div class="">thanks</div><div class="">al;</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Mar 2, 2016, at 11:04 AM, Nicolas Charles <<a href="mailto:nicolas.charles@normation.com" class="">nicolas.charles@normation.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<div class="moz-cite-prefix">Ha - it seems a lot like this issue,
that has been solved last week :
<a class="moz-txt-link-freetext" href="http://www.rudder-project.org/redmine/issues/7975">http://www.rudder-project.org/redmine/issues/7975</a><br class="">
Basically, here, you are missing some reports on the Technique,
hence the errors in reports.<br class="">
You can either wait for the release, upgrade Rudder (and don't
forget to upgrade your techniques :
<a class="moz-txt-link-freetext" href="http://www.rudder-project.org/rudder-doc-3.1/rudder-doc.html#_technique_upgrade">http://www.rudder-project.org/rudder-doc-3.1/rudder-doc.html#_technique_upgrade</a>
), or apply the fix directly on your technique<br class="">
<br class="">
Nicolas<br class="">
<br class="">
<br class="">
Le 02/03/2016 16:55, Al Joslin a écrit :<br class="">
</div>
<blockquote cite="mid:6A902B0E-3679-4C84-A71F-B4DA39BC0404@gmail.com" type="cite" class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
enclosed - more screenshots
<div class=""><br class="">
</div>
<div class="">no, not much - it’s claiming failure on the service
starting parameters — which could only be a little more simple
(don’t change) but then that would obviate the need for this
directive...</div>
<div class=""><br class="">
</div>
<div class=""><span id="cid:part1.04090200.05000403@normation.com" class=""><Mail Attachment.png></span></div>
<div class=""><br class="">
</div>
<div class=""><span id="cid:part2.06070207.04020905@normation.com" class=""><Mail Attachment.png></span><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Mar 2, 2016, at 10:35 AM, Nicolas Charles
<<a moz-do-not-send="true" href="mailto:nicolas.charles@normation.com" class="">nicolas.charles@normation.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<div class="moz-cite-prefix">Hello Al,<br class="">
<br class="">
I've looked at the log, and they indeed don't exhibit
errors. But from what I understand on your screenshot,
you have only a couple of percent of unknow reports -
so the error may lies somewhere else<br class="">
<br class="">
On the Configuration Policy / Rule page, you'll have
the list of rules + their compliance. If you click on
it, you'll see the detail by Directive and by Node,
and you can drill down to pinpoint where the error is.<br class="">
<br class="">
Does it help?<br class="">
<br class="">
Nicolas<br class="">
<br class="">
Le 29/02/2016 16:01, Al Joslin a écrit :<br class="">
</div>
<blockquote cite="mid:A3DA95B2-CF80-4D2F-8695-34078D01F389@gmail.com" type="cite" class="">
<pre class="" wrap="">Hello All,
I must be missing something here….
I’ve constructed a Rudder rule to install the Zabbix-Agent — everything works ok until it gets to the part where I ask it to ensure that the service is running and will restart on boot
The log on the target machine shows no errors and yet the dashboard says 100% failure…
What is going on?
Al;
attachments: service config & log from target machine
</pre>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre class="" wrap="">_______________________________________________
rudder-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:rudder-users@lists.rudder-project.org">rudder-users@lists.rudder-project.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.rudder-project.org/mailman/listinfo/rudder-users">http://www.rudder-project.org/mailman/listinfo/rudder-users</a>
</pre>
</blockquote>
<br class="">
<br class="">
<pre class="moz-signature" cols="72">--
Nicolas CHARLES</pre>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</blockquote>
<br class="">
<br class="">
<pre class="moz-signature" cols="72">--
Nicolas CHARLES</pre>
</div>
</div></blockquote></div><br class=""></div></div></blockquote></div><br class=""></div></body></html>