Sexy`
I'll give it a try thanks again Nicolas ;)
Hey, I'm trying to install a .deb file with the help of Rudder if the currently installed version on the node is older than X. The problem now is that some nodes already have a newer version than the one I'm trying to install. But the generic methods all require an exact version number to check for and you can't specify ranges. I looked in the documentation if there is a way to check if the installed version of a package is <= X and found for example "package_install_version_cmp" (https://docs.rudder.io/reference/6.2/reference/generic_methods.html#_package_install_version_cmp). but this generic method is marked as deprecated and one is supposed to use "package_present". But there is no such functionality specified for "package_present".
Hey Guys, I have a strange behaviour with my rudder server.
We monitor the compliance's status and everyday I have an alert saying I only have 99% compliance. When I check my node some have rule in error BUT when I launch the agent's run everything goes green again. I think it's related to my report. Is anything I can do to not have those false alarm ? cheer team :)
We monitor the compliance's status and everyday I have an alert saying I only have 99% compliance. When I check my node some have rule in error BUT when I launch the agent's run everything goes green again. I think it's related to my report. Is anything I can do to not have those false alarm ? cheer team :)
45 replies
hi guys, wonder if you can help. we originally had a rudder server which worked fine, we then decided to backup and migrate to another server in a different location and ever since we get "Starting Jetty: . . . . . . . . . . . . . . . FAILED Thu Apr 28 10:43:30 BST 2022" almost constantly. occasionly the service will start and report OK but most of the time fails. any ideas?
146 replies
i used your official guide, with the latest version (at the time v7)
Hi guys, is anyone get this error yet ?
/opt/rudder/bin/run-inventory --local=/var/rudder/tmp/inventory/prod-c2d09dd7-a6d8-4eec-8812-297506ff2a92.ocs
[info] FusionInventory instance: builtin
Encode.c: loadable library and perl binaries are mismatched (got handshake key 0xce00080, needed 0xed00080)
I thought at first my perl wasn't up to date
but it's seem ok
Try to force install encode with cpan but so far no luck :'(
like debian10 agent on a debian11
Someone fuck my repo up so
Thanks Nicolas
I know not available yet but I was hype for the 7.1
Which operating system si it on? What does your repo URL look like?
Hi
[Rudder_6.2]
name=Rudder 6.2
username=xxxxxx
password=xxxxxxx
baseurl=http://download.rudder.io/rpm/6.2/RHEL_7/
gpgcheck=1
gpgkey=https://download.rudder.io/rpm/rudder_rpm_key.pub
name=Rudder 6.2
username=xxxxxx
password=xxxxxxx
baseurl=http://download.rudder.io/rpm/6.2/RHEL_7/
gpgcheck=1
gpgkey=https://download.rudder.io/rpm/rudder_rpm_key.pub
i changed to 7.0
in name and baseurl
Hi,
I've updated my Rudder server from 6.2 to 7.1. I've done this by updating the repository and then ran:
zypper up rudder-server-root rudder-server-relay rudder-reports rudder-webapp rudder-agent
Upgrade went fine, no errors reported etc. There is however now one issue. The compliance of the nodes dropped from 100% to 0%. When checking on the individual nodes they all report this error: "No recent reports have been received for this node in the grace period since the last configuration policy change."
So as a test on some of the nodes I changed some resources managed by Rudder and ran the agent. And that ran without any problem at all. Everything was corrected by Rudder as expected.
As I figured that maybe this was due to the 6.2 version of the agent still runnnig on the nodes, I upgraded that on some of them as well to 7.1. Still no luck.
Then I thought that maybe it needed some time to update the reports again. But it has been over 4 hours by now and I'm still at 0% compliance.
I'm running this on SLES15 SP3. I took a snapshot of the VM running the Rudder server before the upgrade, so I could revert back to that. (If I haven't solved it by Monday I guess it will come to that), but I prefer not to do this. So if someone could help me fix this, that would be greatly appreciated.
30 replies
hello, I've a strange behaviour with my template, I create a Technic to deploy custom php.ini.
I create a template : /var/rudder/configuration-repository/shared-files/common/configuration-template/PHP/conf/php.ini.tpl
The file exist and if I cat it I've everything I put inside. But when I deploy the template throught "file from remote template" my agent repaired it but the file is empty...
I create a template : /var/rudder/configuration-repository/shared-files/common/configuration-template/PHP/conf/php.ini.tpl
The file exist and if I cat it I've everything I put inside. But when I deploy the template throught "file from remote template" my agent repaired it but the file is empty...
rudder agent -u -g -i output :
2022-05-16T15:26:33+00:00 rudder info: Created file '/var/rudder/cfengine-community/tmp/templates/file_from_remote_template//etc/php/8.0/fpm/php.ini.datastate.78436.json', mode 0600
2022-05-16T15:26:33+00:00 rudder info: Updated rendering of '/var/rudder/cfengine-community/tmp/templates/file_from_remote_template//etc/php/8.0/fpm/php.ini.datastate.78436.json' from mustache template '/var/rudder/cfengine-community/modules/templates/datastate.json.tpl'
2022-05-16T15:26:34+00:00 rudder info: Copied file '/var/rudder/cfengine-community/tmp/templates/file_from_remote_template//etc/php/8.0/fpm/php.ini.78436.new' to '/etc/php/8.0/fpm/php.ini.cfnew' (permissions preserved)
2022-05-16T15:26:34+00:00 rudder info: Moved '/etc/php/8.0/fpm/php.ini.cfnew' to '/etc/php/8.0/fpm/php.ini'
2022-05-16T15:26:34+00:00 rudder info: Updated file '/etc/php/8.0/fpm/php.ini' from 'localhost:/var/rudder/cfengine-community/tmp/templates/file_from_remote_template//etc/php/8.0/fpm/php.ini.78436.new'
info optimisation___php_fpm Deploy php.ini Conf /etc/php/8.0/fpm/| Copying /etc/php/8.0/fpm/php.ini from /var/rudder/cfengine-community/tmp/templates/file_from_remote_template//etc/php/8.0/fpm/php.ini.78436.new was repaired
info optimisation___php_fpm Deploy php.ini Conf /etc/php/8.0/fpm/| Copying /etc/php/8.0/fpm/php.ini from local /var/rudder/cfengine-community/tmp/templates/file_from_remote_template//etc/php/8.0/fpm/php.ini.78436.new, recursion level 0 was repaired
info optimisation___php_fpm Deploy php.ini Conf /etc/php/8.0/fpm/| Copying /etc/php/8.0/fpm/php.ini from local /var/rudder/cfengine-community/tmp/templates/file_from_remote_template//etc/php/8.0/fpm/php.ini.78436.new was repaired
2022-05-16T15:26:34+00:00 rudder info: Deleted file '/var/rudder/cfengine-community/tmp/templates/file_from_remote_template//etc/php/8.0/fpm/php.ini.datastate.78436.json'
info optimisation___php_fpm Deploy php.ini Conf /etc/php/8.0/fpm/| Remove file /var/rudder/cfengine-community/tmp/templates/file_from_remote_template//etc/php/8.0/fpm/php.ini.datastate.78436.json was repaired
2022-05-16T15:26:34+00:00 rudder info: Deleted file '/var/rudder/cfengine-community/tmp/templates/file_from_remote_template//etc/php/8.0/fpm/php.ini.78436.new'
info optimisation___php_fpm Deploy php.ini Conf /etc/php/8.0/fpm/| Remove file /var/rudder/cfengine-community/tmp/templates/file_from_remote_template//etc/php/8.0/fpm/php.ini.78436.new was repaired
info optimisation___php_fpm Deploy php.ini Conf /etc/php/8.0/fpm/| Build file /etc/php/8.0/fpm/php.ini from jinja2 template /var/rudder/cfengine-community/tmp/templates/file_from_remote_template//etc/php/8.0/fpm/php.ini was repaired
info optimisation___php_fpm Deploy php.ini Conf /etc/php/8.0/fpm/| Build file /etc/php/8.0/fpm/php.ini from jinja2 template /var/rudder/cfengine-community/tmp/templates/file_from_remote_template//etc/php/8.0/fpm/php.ini was repaired
E| repaired optimisation___php_fpm Deploy php.ini Conf /etc/php/8.0/fpm/| Build file /etc/php/8.0/fpm/php.ini from template /var/rudder/configuration-repository/shared-files/common/configuration-template/PHP/conf/php.ini.tpl was repaired{
"disable_functions": "XXX,syslog,openlog,closelog,posix_kill,posix_getpwuid,dl,exec,system,shell_exec,proc_open,popen,passthru",
"exectime": "30",
"maxinputtime": "30",
"maxinputvars": "30",
"memorylimit": "256M",
"timezone": "Europe/Paris",
"uploadmaxfilesize": "100M"
}
Exectime doesn't work
I tried to update my jinja2 template and use other variable and no problem
I tried to change the variable name to exectime (before was maxexectim)
And I still can't using it or my php.ini end up empty :'(
now it works...
I spend yersterday on this problem
and I didn't touch anything and now it works
