Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    pablo-qb
    @pablo-qb
    It worked as it, I've ran rudder agent update -v without closing debug
    pmg
    @pmg7557_twitter
    @ncharles @amousset Hello Alexis & Nicolas, I did not send you the file on dev@rudder.io this the pb is not linked to this. See my post at 8h41, this file is empty on another node!
    GUI experience. On the GUI you can see the compliance by node & by directive. I have 10% 'Missing report' on the directive 'Scheduled Jobs', how can I know which nodes are concerned?
    Nicolas Charles
    @ncharles
    yes, on the rules details, you can drill done on nodes, and see which are not compliant
    pmg
    @pmg7557_twitter
    @ncharles I don't understand your answer. We can see compliance per rule but not per directive, isn'it?
    Nicolas Charles
    @ncharles
    on the rule itself
    if you click on the Rule name, you have a "compliance" tab
    with compliance per node and per directive within the rule
    pmg
    @pmg7557_twitter
    @ncharles Yes, but it's per directive for all the nodes or per node for all the directives, I cannot see the nodes which don't match a specific directive...
    Nicolas Charles
    @ncharles
    Ha !
    your initial message was to know which nodes are in 'missing report' for 'scheduled jobs'
    pmg
    @pmg7557_twitter
    @ncharles Yes but 'scheduled jobs' is a direcive included in a rule 'Global config for all nodes'
    @ncharles That's said, I have no more pb this morning, I decreased the 'running period' from 6h period/5h max delay to 2h period / 1h max delay. Can this be an explanation? How I can go back to 6h h period and avoid the 'scheduled job missing report'?
    Nicolas Charles
    @ncharles
    @pmg I'm unsure of your question
    if you go on the Rule page, click on 'Global config for all nodes' it will open on the bottom a display to configure the rule (Settings), but also a tab for Compliance. There you have compliance by Directive, and can select the scheduled jobs. It will unfold the compliance, and you'll see the components of the Directives, if you click again on the component, you have the list of nodes it's applied to, and the compliance status for each node
    @pmg7557_twitter What is the configuration of the directive? What's the expected time execution of the command?
    pmg
    @pmg7557_twitter
    @ncharles "if you click again on the component, you have the list of nodes it's applied to, and the compliance status for each node" Not clear for me, when I had 2 directives with compliances pb in the same rules, I did not find a way to list the nodes concerned by each pb. I have no pb at that moment, I'll see that point later ...
    pmg
    @pmg7557_twitter
    configuration of the directive :
    Lowest time the command should be run at 1
    Highest time the command should be run at 4
    Consider the job failed after (minutes) 120
    Return codes considered as a success 0
    Return codes considered as a repair 1
    Return codes considered as an error 2
    expected time execution : variable from ~0 to ~1h
    pmg
    @pmg7557_twitter
    Probably because : period of 6h and run between 1 to 4 ... ?
    Nicolas Charles
    @ncharles
    ha, that's "interesting"
    that's clearly a bug. Would you mind opening a ticket for this one ?
    pmg
    @pmg7557_twitter
    @ncharles Done : Demande #18203 créée. Hope it is clear.
    Nicolas Charles
    @ncharles
    crystal clear
    thank you
    norbertoaquino
    @norbertoaquino
    Hello, I am planning to install PostgreSQL on a separate machine, which version of PostgreSQL is supported with rudder?
    Alexis Mousset
    @amousset
    At least 9.2 for Rudder 6.1 IIRC
    10 recommended
    cc @ncharles
    Francois Armand
    @fanf
    yep, that's it
    actually: any postgres newer than 9.2 will work, we just don't use newer feature to remain compatible. But with newer version, you will benefits from all perf/tooling/etc enhancements of postgres
    norbertoaquino
    @norbertoaquino
    Great! thank you @fanf @amousset
    Nicolas Charles
    @ncharles
    Latest postgresql is the best choice if possible
    realitygaps
    @realitygaps
    We have noticed that slapd is regularly spiking to 85+% cpu on our rudder server. Is there a known issue related to this?
    its version 6.0.9
    Alexis Mousset
    @amousset
    can it be during policy generation?
    realitygaps
    @realitygaps
    hmm it could be, how would i easily check?
    im not manually generating them when it happens
    Alexis Mousset
    @amousset
    they can happen automatically when there are changes in inventories or applied policies
    realitygaps
    @realitygaps
    there werent any changes being made in the past day
    Alexis Mousset
    @amousset
    do you have monitoring graphs showing this behavior?
    realitygaps
    @realitygaps
    am checking. it seems the largest spikes are indeed at midnight which makes sense. but the last couple of days there has been more occurrences outside of that time
    i have some basic cpu graphs
    seems only to be after the update to 6.0.9 that it spiked at other times
    but i will keep an eye on it the coming day and see
    also, are there any risks from doing a vacuum?
    Nicolas Charles
    @ncharles
    It is most likely when you receive inventories
    at midnight there are also maintenance of the database, that uses resources.
    Doing a simple vacuum (or vacuum analyze) on the database is pretty safe. Avoid doing it around midnight, and if you can increase maintenance_work_mem before it would help making it faster
    If you can identify when were the spikes, you can check on the Event Logs (Utilities/event logs page) to see what happened at that time
    Finally, 6.1 improves the slapd part by adding indexes. It does help slapd a lot