done.. regenerating the polies takes much longer now!!
cool!! I still have one error.. but this seems to be an old agent??
⇨ Unexpected: Generation ended but some nodes were in errors: Error while building target configuration node for node '798c933f-0f4f-496a-ab75-083c0f20b9b0' which is one of the target of rules. Ignoring it for the rest of the process
⇨ Node ahk-prdidm02.xxxxxxl (798c933f-0f4f-496a-ab75-083c0f20b9b0) has an agent which doesn't support sending compliance reports in HTTPS: Rudder agent only support HTTPS reporting for version >= 6.0. You need to either disable that node (in node details > settings > Node State) or update agent version on that node
⇨ Unexpected: Generation ended but some nodes were in errors: Error while building target configuration node for node '798c933f-0f4f-496a-ab75-083c0f20b9b0' which is one of the target of rules. Ignoring it for the rest of the process
⇨ Node ahk-prdidm02.xxxxxxl (798c933f-0f4f-496a-ab75-083c0f20b9b0) has an agent which doesn't support sending compliance reports in HTTPS: Rudder agent only support HTTPS reporting for version >= 6.0. You need to either disable that node (in node details > settings > Node State) or update agent version on that node
I'll start with the disable optien
yes, it is an agent which is just too old for 7.0 more secured protocols (actually, 6.x supported both but the old protocol was removed in 7.0)
just to know: why did you upgraded to 7.0 and 7.1 ? 7.0 is almost EOL (and 7.2 is out early next week, with a much refined UI and other cool things)
hey, you seems to use rudder since a very very long time since you have pre-6.0 agent. May I ask you since when ?
I do see still see an error in the stout file..
2022-09-23 12:36:18.124:WARN:oejs.session:qtp644345897-13:
java.lang.IllegalStateException: Not started
2022-09-23 12:36:18.124:WARN:oejs.session:qtp644345897-13:
java.lang.IllegalStateException: Not started
Oh fixed it with a jetty restart I think :D
wow, 5 years is huge :) We welcome feedbacks, especially from long term users, so don't hesitate (even via private email if you prefer)
you can contact me at francois@rudder.io, or the dev team is available at rudder@rudder.io (and of course, for general info etc, you can use the contact form on the website)
for the illegalestateerror: it's nothing. It's an exception that is raised when we stop the java server (restart rudder for ex), and we didn't found a way to hide it. It's extremely frustrating, misleading, but armless
@Fdall , here is the error => Inventory script (/home/adminmis/ansible/ansible-tnsnames/rudder.py) had an execution error: ERROR: "Name collision on hosts:
Unable to parse /home/adminmis/ansible/ansible-tnsnames/rudder.py as an inventory source
@skygeneve Ok, looks like an ansible error when it finds multiples hosts defined with the same name in the inventory. Can you try to run the rudder.py script without ansible and find the hosts defined multiple times? You should be able to identify them by running either
./rudder.py | jq '._meta.hostvars | keys' or ./rudder.py | jq 'keys'
It can happen if you have rudder nodes with similar hostname or groups with almost similar names
hello, i'm trying to acces node item "properties" through REST API with python, but it seems they aren't all available.
Using this syntax :
node = {"objectType": "node", "attribute": "properties",
"comparator": "eq", "value": "foo"}
And get this as a return :
{"action":"listAcceptedNodes","result":"error","errorDetails":"The attribute 'properties' is unknown for type 'node' in line 'StringCriterionLine(node,properties,eq,Some(foo))'. Possible attributes: [OS, agentName, inventoryDate, ipHostNumber, localAccountName, localAdministratorAccountName, nodeHostname, nodeId, osArchitectureType, osFullName, osKernelVersion, osName, osServicePack, osVersion, policyServerId, ram, state, swap]"}
Using this syntax :
node = {"objectType": "node", "attribute": "properties",
"comparator": "eq", "value": "foo"}
And get this as a return :
{"action":"listAcceptedNodes","result":"error","errorDetails":"The attribute 'properties' is unknown for type 'node' in line 'StringCriterionLine(node,properties,eq,Some(foo))'. Possible attributes: [OS, agentName, inventoryDate, ipHostNumber, localAccountName, localAdministratorAccountName, nodeHostname, nodeId, osArchitectureType, osFullName, osKernelVersion, osName, osServicePack, osVersion, policyServerId, ram, state, swap]"}
I think i'm not using the right syntax but could not find anything helping in documentation
1 reply
hello thank you for your reply! sorry for not being clear enough...i'm trying ^^
Actually i'm trying to list nodes with only selected properties...for exemple get minimal,os, lastInventoryDate,lastRunDate, properties named y and z
Actually i'm trying to list nodes with only selected properties...for exemple get minimal,os, lastInventoryDate,lastRunDate, properties named y and z
3 replies
i was thinking about that but file with minimal and properties is about 900k lines, not sure if you quilify this as huge ^^
1 reply
ok thank you very much for the advice, most nodes will have the expected props, so i will post filter. Have a nice Week end !
1 reply
Hello everyone. No issue today, just questions : Our setup is using the builtin directive Rudder SNMP Configuration, for which I suppose is :
- ensuring that the snmpd daemon is installed and running
- doing something on /etc/snmp/snmpd.conf [1]
For this point [1], I'm witnessing that any manual change on this file is not overwritten by the directive, which behaviour I was expecting.
Before going any further, may someone tell me if Rudder 7.2.0 is still using this snmpd mecanism for internal purposes, or has it been superseded by something newer?
2 replies
with a jinja template
"where": [
{
"objectType": "node",
"attribute": "properties",
"comparator": "eq",
"value": "client=toto"
}
Is it the right way to use the where ?
nvm found it
yes, the inventory is the source of truth for inventories things (ie not properties, which their source of truth comes from... It depends :) Groups, user defined, data sources, inventory hooks...)
it's the same idea with node create api (plugin < 7.2, native in 7.2), things that are set-up via the API are overridden by the next inventory (apart properties, as ever)
:D
Ok it's ui related but :)
How can I contribute to rudder-tools ? Just a PR ?
3 replies
ok, I think there is no pb, especially for self contained things like that
(ie: sure, go on :) )