Hey guys. I'm just decommissioning a few servers that are running rudder 2.10 (yes, really). I'm trying to remember what the file to create to disable the agent is but I'm pulling a blank. I thought it was something like /opt/rudder/etc/agent-disable or disable-agent or something like that, but the agent still seems to be enforcing policies... Any ideas?
create a custom domain for my node's communication
@Elenui I tried to follow this but am not sure if I am doing something wrong
Hello! Sorry, think this is not the correct place to write this, but I can't find any place where to report the issue so maybe someone can point me in the right direction... The problem is this: in the official rudder repositories, the "latest" link still points to the 6.2 version while 7.0 is out. Does anyone know how I can alert normation about this? Many thanks!
if you need, you can of course already use ../7.0/... url
Hello. How can I manually make a node run its rudder-hooks and inform the hub? (rudder agent inventory doesn't seem to do it)
Is the hook executable ?
does it returns valid json ?
yes it is
you can run manually the inventory with /opt/rudder//bin/run-inventory --debug --local=/tmp/inv.ocs and check the content of the inventory for tag CUSTOM_PROPERTIES
@ncharles OK, this does work, and I can see that what's in the CUSTOM_PROPERTIES is current with what I expected. But is there a way to manually (force) this result to be sent to the hub? I mean, I know that every night this very action is done correctly, but how to manually trigger it on demand?
rudder agent inventory
OK, thanks. I thought that when running inventory manually, the results were not routed to the hub. I thought that because some dynamic groups are based on properties, and I have to manually refresh them to see the group content change.
Dynamic groups are always refreshed when new inventory arrive, or also every 5 minutes, just to check
:information_source: Rudder is not impacted by the spring4shell vulnerability (CVE-2022-22965)
Should the Condition for OS match on Techniques do this: Skipping method 'File from HTTP server' with key parameter '/opt/uptic/software/zabbix/zabbix-release_5.0-1+focal_all.deb' since condition 'ubuntu_20_4.(directory_presentopt_uptic_software_zabbixok)' is not reached was not applicable
show as ubuntu_20_4
as i cant seem to get this condition to trigger for ubuntu 20.04 and all i see is via the dropdown ubuntu major 20, minor. 4
but cant add 20 04 as the minor
@mattronix Your best bet is to run rudder agent info -v on your ubuntu node, and look for the most precise system condition defined. Still, ubuntu_20_4 looks correct
cant figure out whats blocking my run
did not know those exist condtion wise
looks like a bug indeed as look ubuntu 20_04 is listed