[rudder-users] need help getting 100% compliance w/simple service script
Al Joslin
allen.joslin at gmail.com
Thu Mar 3 17:16:37 CET 2016
not to worry, it’s all in a days work for ‘why is everything so hard?’ man!
:)
I pulled the raw from a different place - http://www.rudder-project.org/redmine/projects/rudder/repository/rudder-techniques/revisions/ea8dd328300427beacc91cc4d9ee84b27a642d5a/entry/techniques/systemSettings/process/servicesManagement/3.0/servicesManagement.st <http://www.rudder-project.org/redmine/projects/rudder/repository/rudder-techniques/revisions/ea8dd328300427beacc91cc4d9ee84b27a642d5a/entry/techniques/systemSettings/process/servicesManagement/3.0/servicesManagement.st>
diff says they are identical — so it must have been about how I installed it
I had copied it into the two places I found the original — in /opt/rudder/… and /var/rudder/… the /var/ copy was under git control, so I added it and committed the change.
what is the better way? why are there two locations, is one of them for DIST originals?
I don’t have a Policy Server tab, but I find "Update Techniques now" at the bottom of Admin->Settings — the blurb mentions the /var/… location as it’s source...
I had a red x not a green check - so generation was not successful
Once you clarify where I should place the file I will try again
thanks!
al;
p.s. I would a Networking->Port Management technique — is one on the horizon? Or should I have a go at it?
> On Mar 3, 2016, at 3:50 AM, Nicolas Charles <nicolas.charles at normation.com> wrote:
>
> Hello Al,
>
> I'm sorry you had such a bad experience.
> Did you copy the content of the file, or the html content of the page (it looks like a dumb question, but I've already wget in the past the pages, and got caught by html in my code:))
> Raw version can be found here:
> https://raw.githubusercontent.com/amousset/rudder-techniques/ea8dd328300427beacc91cc4d9ee84b27a642d5a/techniques/systemSettings/process/servicesManagement/3.0/servicesManagement.st <https://raw.githubusercontent.com/amousset/rudder-techniques/ea8dd328300427beacc91cc4d9ee84b27a642d5a/techniques/systemSettings/process/servicesManagement/3.0/servicesManagement.st>
>
> And you were missing the last step of the technique update, which is (stated from doc):
> "go to the Rudder web interface, to the Administration tab, Policy Server tab, and click on "Reload Techniques". It will reload the Technique library and trigger a full redeployment on nodes."
> Otherwise, Rudder may not see that there is a change.
>
> However, I don't understand why compliance wheel was spinning. Was the generation successfully ? (Successful generation is a green tick on the top right hand side corner, failed on is a red cross)
>
> Nicolas
>
> Le 02/03/2016 23:30, Al Joslin a écrit :
>> I’ve restored the serve to a prior snapshot
>>
>> I had to run rudder agent reinit to get the nodes to show up and be accepted again
>>
>> I am back to where I was before the wind blew
>>
>> Awaiting suggestions
>>
>> Al;
>>
>>
>>
>>
>>> On Mar 2, 2016, at 12:23 PM, Al Joslin < <mailto:allen.joslin at gmail.com>allen.joslin at gmail.com <mailto:allen.joslin at gmail.com>> wrote:
>>>
>>> I threw caution to the wind and installed the revised servicesManagement.st <http://servicesmanagement.st/>
>>>
>>> I copied it from:
>>> <http://www.rudder-project.org/redmine/projects/rudder/repository/rudder-techniques/revisions/ea8dd328300427beacc91cc4d9ee84b27a642d5a/entry/techniques/systemSettings/process/servicesManagement/3.0/servicesManagement.st>http://www.rudder-project.org/redmine/projects/rudder/repository/rudder-techniques/revisions/ea8dd328300427beacc91cc4d9ee84b27a642d5a/entry/techniques/systemSettings/process/servicesManagement/3.0/servicesManagement.st <http://www.rudder-project.org/redmine/projects/rudder/repository/rudder-techniques/revisions/ea8dd328300427beacc91cc4d9ee84b27a642d5a/entry/techniques/systemSettings/process/servicesManagement/3.0/servicesManagement.st>
>>> Into:
>>> /opt/rudder/share/techniques/systemSettings/process/servicesManagement/3.0/servicesManagement.st <http://servicesmanagement.st/>
>>> /var/rudder/configuration-repository/techniques/systemSettings/process/servicesManagement/3.0/servicesManagement.st <http://servicesmanagement.st/>
>>> (committing the change to git [from within the 3.0 folder] in the latter case)
>>>
>>> Rudder didn’t see that as a change so nothing was applied
>>>
>>> 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
>>>
>>> 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
>>>
>>> So I deleted and rebuilt my directive instance, which caused the Rules to be applied as soon as the deletion was applied
>>> - I guess I should have disabled them to make changes?
>>>
>>> Then I re-added the new instance of the serviceManagement directive to the rules - in their settings panes
>>>
>>> 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…
>>>
>>> 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
>>>
>>> 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
>>>
>>> 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
>>>
>>> OK, so I’m kinda wishing I’d waited for the release…
>>>
>>> Suggestions? Options?
>>>
>>> thanks
>>> al;
>>>
>>>
>>>
>>>
>>>> On Mar 2, 2016, at 11:04 AM, Nicolas Charles <nicolas.charles at normation.com <mailto:nicolas.charles at normation.com>> wrote:
>>>>
>>>> Ha - it seems a lot like this issue, that has been solved last week : http://www.rudder-project.org/redmine/issues/7975 <http://www.rudder-project.org/redmine/issues/7975>
>>>> Basically, here, you are missing some reports on the Technique, hence the errors in reports.
>>>> You can either wait for the release, upgrade Rudder (and don't forget to upgrade your techniques : 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> ), or apply the fix directly on your technique
>>>>
>>>> Nicolas
>>>>
>>>>
>>>> Le 02/03/2016 16:55, Al Joslin a écrit :
>>>>> enclosed - more screenshots
>>>>>
>>>>> 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...
>>>>>
>>>>> <Mail Attachment.png>
>>>>>
>>>>> <Mail Attachment.png>
>>>>>> On Mar 2, 2016, at 10:35 AM, Nicolas Charles < <mailto:nicolas.charles at normation.com>nicolas.charles at normation.com <mailto:nicolas.charles at normation.com>> wrote:
>>>>>>
>>>>>> Hello Al,
>>>>>>
>>>>>> 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
>>>>>>
>>>>>> 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.
>>>>>>
>>>>>> Does it help?
>>>>>>
>>>>>> Nicolas
>>>>>>
>>>>>> Le 29/02/2016 16:01, Al Joslin a écrit :
>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> rudder-users mailing list
>>>>>>> rudder-users at lists.rudder-project.org <mailto:rudder-users at lists.rudder-project.org>
>>>>>>> http://www.rudder-project.org/mailman/listinfo/rudder-users <http://www.rudder-project.org/mailman/listinfo/rudder-users>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Nicolas CHARLES
>>>>>
>>>>
>>>>
>>>> --
>>>> Nicolas CHARLES
>>>
>>
>
>
> --
> Nicolas CHARLES
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rudder-project.org/pipermail/rudder-users/attachments/20160303/cc252ee2/attachment-0001.html>
More information about the rudder-users
mailing list