udder=# \dt
Liste des relations
Schéma | Nom | Type | Propriétaire
--------+----------------------------+-------+--------------
public | archivednodecompliance | table | rudder
public | archivednodeconfigurations | table | rudder
public | archivedruddersysevents | table | rudder
public | campaignevents | table | rudder
public | changerequest | table | rudder
public | eventlog | table | rudder
public | gitcommit | table | rudder
public | migrationeventlog | table | rudder
public | nodecompliance | table | rudder
public | nodecompliancelevels | table | rudder
public | nodeconfigurations | table | rudder
public | nodes_info | table | rudder
public | reportsexecution | table | rudder
public | rudderproperties | table | rudder
public | ruddersysevents | table | rudder
public | statusupdate | table | rudder
public | workflow | table | rudderrudder=# select relname, pg_size_pretty(pg_total_relation_size(relname::regclass)) as full_size, pg_size_pretty(pg_relation_size(relname::regclass)) as table_size, pg_size_pretty(pg_total_relation_size(relname::regclass) - pg_relation_size(relname::regclass)) as index_size from pg_stat_user_tables order by pg_total_relation_size(relname::regclass) desc limit 10;
relname | full_size | table_size | index_size
----------------------+-----------+------------+------------
ruddersysevents | 12 GB | 9525 MB | 2734 MB
nodecompliancelevels | 1873 MB | 1000 MB | 873 MB
reportsexecution | 120 MB | 51 MB | 69 MB
eventlog | 53 MB | 32 MB | 21 MB
nodeconfigurations | 19 MB | 864 kB | 18 MB
gitcommit | 952 kB | 496 kB | 456 kB
nodes_info | 640 kB | 544 kB | 96 kB
rudderproperties | 64 kB | 8192 bytes | 56 kB
statusupdate | 64 kB | 8192 bytes | 56 kB
nodecompliance | 40 kB | 0 bytes | 40 kB
We suppose it's ruddersysevents since it's the biggest one
@astropat73_gitlab: ok, so likely, what is happening:
- for some reason, the performance of your LDAP server are degraded. So typically, when it tries to "delete" a node, what happens is - don't forget that by default, nodes are moved to "deleted" branch, not really erase -: start of deletion process, node entries are moved to deleted branchs ; that stalls; the next node deletion tasks are started, like changing the node certificate status - but the node entry is not yet commited ; that fails.
What you can do: - change the property "rudder.nodes.delete.defaultMode" to "erase" so that nodes are really deleted ;
- try to understand why that LDAP is so slow. There is no standard process for that unfortunatly
9 replies
to fix the doc ?
@ellenui_twitter: yes.
We identified a pb with a new feature that cause bad postgresql performances. The request
A first workaround seems to be adding an index, and we are looking for a definitive solution:
We identified a pb with a new feature that cause bad postgresql performances. The request
select id, executiondate, ruleid, directiveid, nodeid, reportid, component, keyvalue, executiontimestamp, eventtype, msg from ruddersysevents where 1=1 and id >= '0' and (eventtype='report_json') order by id asc limit 1000;.A first workaround seems to be adding an index, and we are looking for a definitive solution:
"event_report_json_idx" btree (id) WHERE eventtype = 'report_json'::text
as always ^ ^
Cause we get almost 1Go/s Read on our rudder XD
thanks VSAN
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 ?
if it's that, there is no way by UI, and only complicated way by API. The simplest would be to just open the two directives and copy/paste
oh, you must not go through the login page, else other session get disconnected
I just did -^
else you can also "middle-click" to open a new tab, and then drag the tab out of the line of firefox open tabs, it will transform the tab into a window
happy to have helped !
we actually remove the login form redirection from base URL when already corrected in 7.3. Maybe we could backport this as a bugfix https://issues.rudder.io/issues/21807.
Hello all, incredibly new here. I am trying to get rudder installed on RHEL9. I followed the guide (https://docs.rudder.io/reference/7.2/installation/server/rhel.html#_initial_configuration) but it does not mention executing the rudder-init script. That is not correct, is it?
@H3ROE: not at all, you came here to say hello, and we are very glad to meet you. Happy rudder! Don't hesitate to ask if needed.
I don't recall how but you can download free plugin from https://github.com/Normation/rudder-plugins and install it from cli
you don't need an account
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
4 replies
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)
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)
18 replies
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?
5 replies
Dear community !We want to better understand who are the Rudder users are and what their needs are. You can help us by filling out this survey https://rudder.limesurvey.net/618177