normation/rudder

Continuous Auditing & Configuration - please speak english and be nice ;)

Elenui

@Elenui

You can set up some properties like : servertype : Front

and inside your jinja template create a condition that will generate the perfect configuration file for you server

I use the copy from remote template to do this for all my snmpd.conf

For doing this I use the local properties. I created a small script that scan the server and create a properties files

when snmpd conf jobs runs it'll use the local properties and generate the snmpd.conf that fit the server


{%- if vars.node.properties.role.useSSL %}
extend check_ssl /usr/bin/sudo /opt/snmp/check_ssl_validity.sh
{%- endif %}

for exemple

And with this way you have one template to manage with your git repo and if you make change it'll be deploy on all server

Benjamin Dupalut

@binibitobi_gitlab

Thank you for the explanations. I can use it for other files but the rsyslog.conf is different from one server to another because the services running and logging are not the same.

Elenui

@Elenui

The all file is different ? `

all server are different *

Benjamin Dupalut

@binibitobi_gitlab

Each server does not have a different rsyslog.conf file configuration. Two DNS servers will have the same configuration, for example. But a DHCP server and a DNS server will not have the same configuration for example.

Elenui

@Elenui

understand ^^

Benjamin Dupalut

@binibitobi_gitlab

So, does anyone have any idea how I can verify that the string "@ syslog.xxxxxx.xxx: 514" is present in the /etc/rsyslog.conf files of my servers?

Or can anyone tell me why the augeas method I created is "Compliant" whether the string is present or not?

Benjamin Dupalut

@binibitobi_gitlab

Hello everyone,

Does anyone have an idea please?

Fdall

@Fdall

@binibitobi_gitlab The augeas method does not work that way. Augeas uses lenses to observe the target file, following some pre-defined path. Check the augeas documentation if you want to know more about it.
In your case, the easiest way it most likely to use the file key value present, since your line seems to match the pattern <key><separator><value> with:

@ syslog.xxxxxx as key
: as separator
the port as value

Benjamin Dupalut

@binibitobi_gitlab

Hi @Fdall. Thank you for your reply. I will try this.

Benjamin Dupalut

@binibitobi_gitlab

Hi,

I configured a technique with the file key-value present method but it still indicates non-compliant while the value and the key are present in the file:

Fdall

@Fdall

Erf, I am indeed able to reproduce, this is a bug. I believe it comes from an incorrect escaping somewhere in the method which uses regex. I will try to investigate it this week and let you now, no easy workaround atm

Benjamin Dupalut

@binibitobi_gitlab

Thank you for your reply and your action.

Rana Masud

@mrana_dev_gitlab

Is there any documentation to configure schedule in rudder?

Elenui

@Elenui

hello you mean the agent run schedule ?

14 replies

lpwevers

@lpwevers

Hi Everyone,

Just thought I let you know. If there are people who use CheckMK as their monitoring system, there's now a plugin available for monitoring the status of the Rudder agent. You can download it from the CheckMK Exchange:
https://exchange.checkmk.com/p/rudder

xlbt

@xlbt

Sorry if this question has already been asked, but is there a place to find a copy of a deleted file with the "File absent" method ?
Thanks.

Fdall

@Fdall

Hi @xlbt you can check on your agent under the folder /var/rudder/modified-files, but I am not sure that the agent keep a backup before removing file

xlbt

@xlbt

This is the first place I looked, but unfortunately there is no backup of the deleted file.

Elenui

@Elenui

Hello Team

I'm having trouble with my jetty, i can't find the log. anyone have in thought where it's located ?

get nothing inside : /var/rudder/jetty/lgos

hum ok it's back after a reboot

Tanguy PELADO

@tpelado

Good day everyone,

I'm having some weird bahaviours on node upon upgrading them to our new rudder server.
Some of them won't run the agent automatically, and as such they show up as not running on the server.

rudder agent run is okay and reports not errors.
rudder agent health also reports OK.

This could be some weird cron related stuff, but I wanted to know if there's a known issue

Nicolas Charles

@ncharles

they are in /var/log/rudder/webapp

@tpelado you upgraded to which version ?

if you run rudder agent history on the node, do you see that the agent is run every 5 minutes?

Tanguy PELADO

@tpelado

Running "rudder agent history" shows that the agent doesn't run on its own after upgrading to 6.2 (we were on 4.X)

Elenui

@Elenui

they are in /var/log/rudder/webapp

indeed but it was empty when I check. I thought logs were somewhere else ^^"

Tanguy PELADO

@tpelado

on a side note : it would be a nice feature to have criteria using logic between themselves. As an exemple, you could have a groupe that has ("Node OS = Debian" AND "node Location = DC1") AND NOT "Node property foobar is defined"

a bit like the factorio train stop condition logic, if that talks to anyone (doubt it does :D )

Nicolas Charles

@ncharles

Running "rudder agent history" shows that the agent doesn't run on its own after upgrading to 6.2 (we were on 4.X)

i'm unsure the direct upgrade from 4.x to 6.2 is supported

can you run rudder agent info

it might be that the agent was either disabled, or its uuid modified

Nicolas Charles

@ncharles

if it is disabled, you may run rudder agent enable

Tanguy PELADO

@tpelado

I have removed the agent and factory reseted the node

so that should not be an issue per se

Nicolas Charles

@ncharles

when you factory reset it, you give it a new rudder id

so it's not the same node

Tanguy PELADO

@tpelado

yes, that is correct

Where communities thrive

People

Repo info

Activity