hello @sr57 , I'm not sure I understand. You have two directives derived from the same "file content" technique, and you would like to ? Move a definition block for check on file from one directive to the other ?
@amousset thanks a lot for your answer on my issue. <3
@ellenui_twitter Yeah, I already cloned that github repo, but can't find any pkgs, only the source
Good day all, is there a way to reduce rudder clients log output? Makes the syslog file nearly unusable.
Good day, after upgrading to 7.2 (from 6.2) everything works fine but all reporting seems to not work. The log is constantly throwing this error: "column ruddersysevents.reportid does not exist" - I can't tell if this is a known or novel issue. Didn't find anything in the documentation
Hi, I’ve upgrade to 7.2 some days ago and rudder is constantly restarting. Today I’ve count 24 start in the logs. What could cause that, i see no errors in the logs.
Good morning. I have a physical server that I upgraded from Ubuntu 18 to Ubuntu 22. I was forced to restart it from my backup to Ubuntu 18, but now after 2 days, Rudder (server 7.2 – agent 7.2.1) still shows Ubuntu 22 (in addition Rudder reports the name as « aabb » but hostname is « aa_bb » - don’t remember if I had this behavior before upgrade). Maybe there is st to check before trying to solve this pb (relaunch inventory, reset, recreate node)
Hello everyone. Though I've searched in the doc and in this chat, I didn't find this answer : I'm deploying hook scripts that are setting nodes property, which I'm then using to decide things. This is working fine. In the doc, I've read that the hooks are ran on a daily basis, which is also fine for me. But in case I want to quickly test one change, I thought I could just run "rudder agent inventory" and the hooks were to be ran. I'm not sure that this is the case, but anyway, I'm witnessing that the properties of the tested node are not changing. Is there a way to speed things up manually, in this precise case of a test?
The result will be shown at the Config Management Camp (Ghent, Belgium) in February 2023. Your answer won’t be used for commercial purposes ( unless if you opt-in at the end of the survey to be contacted by the sales team )
hello la dream teeam
tous mes vieux :D
rudder 7 don't work with centos 7 ?
Hi Can anyone explain how to setup Rudder opensource??
Hi all :) I am the CEO of Rudder, and I wish you all a happy new year. I hope you a lot of green dashboard to ensure compliance on your infrastructures! 😁
Hi everyone, is there a way to edit a technique and try it / enable it on one node before it deploys on every node ? We currently have to duplicate everything every time to test a new version we worked on
Can someone provide the Postgresql Upgrade Link for RHEL?
Yes it is AmazonLinux2
Hello All, Error during Rudder 7.2 server installation. -Had a problem on my rudder server 7.2 ran on debian 10 lxc and decided to restore my backup on a fresh new install. -I removed all rudder app following https://docs.rudder.io/reference/7.2/administration/uninstall.html and redid « apt install rudder-server » but the process ended with error : rudder-relay rudder-server E: Sub-process /usr/bin/dpkg returned an error code (1) -The first error msg I saw was : Paramétrage de rudder-relay (7.2.3-debian10) ... chmod: impossible d'accéder à '/opt/rudder/etc/relayd/main.conf': Aucun fichier ou dossier de ce type dpkg: erreur de traitement du paquet rudder-relay (--configure) : -and before I saw also such lines Préparation du dépaquetage de .../62-rudder-relay_7.2.3-debian10_amd64.deb ... Conservation de « détournement de /opt/rudder/etc/relayd/logging.conf en /opt/rudder/etc/relayd/logging.conf.distrib par rudder-relay » -Hope one of you should have an idea, if I should try on a fresh new OS.
Good morning everybody, rudder-jetty failed after restoration on a fresh 7.2 install on debian 11 any explanation/idea to debug?