Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Francois Armand
    @fanf
    hello @wit. That is extremelly strange and a first time encounter for us. Have you more information about it ? Perhaps something in logs? (/var/log/rudder/webapp/2020_03_30.stderrout.log)
    Vincent Membré
    @VinceMacBuche
    wit: On which version of Rudder ? root still has the expecter one, only the relay has changed ?
    @tim-oak How did you rename ? through the technique editor ?
    tim-oak
    @tim-oak
    yepp, renamed it, cloned it and gave the clone the old name
    Rudder Chatbot
    @rudderbot
    wit well the unfortuante thing is that i'm not really sure exactly when it happened. I'll have to go through all the logs and look for clues
    Francois Armand
    @fanf
    @wit: if there's an observable consequence (node not updating, or the like), perhaps you can use that knowmedge to found root cause?
    Rudder Chatbot
    @rudderbot
    wit well I've narrowed it down to the day at least.
    Rudder Chatbot
    @rudderbot
    wit from what I can gather is this... My rudder runs in an lxc container. I recently moved it to a proxmox container. I see issues in the logs complaining about not being able to set up mount namespacing. Nesting has been enabled to fix that error and rudder started working again however it is at this poinbt that the uid of the servers have swapped
    Francois Armand
    @fanf
    @wit if you need help to analyse/narrow it more, don't hesitate to ask - and can also send us info privatly if you want
    Rudder Chatbot
    @rudderbot
    wit how,.... i don't knoe
    wit know*
    tim-oak
    @tim-oak
    ... any ideas how I can fix the cause of those error messages, or get rid of them?
    Each time I open the technique editor there pop up about 20 of them ...
    I I had all policies regenerated through the WebGUI but that didn't changed anything.
    Francois Armand
    @fanf
    @tim-oak : @VinceMacBuche is looking at it, he partially reproduces the problem (or something related).
    tim-oak
    @tim-oak
    thnx ! ! very much appreciated !! xfingers ;-)
    Vincent Membré
    @VinceMacBuche
    What is the content of /var/rudder/configuration-repository/techniques/user_techniques ? and the folder technique within it ?
    You should not be able to rename it with the old base-technique name (because it will generate the same techniqueId andshould be prevented)
    It was prevented at some point in the past, but something has changed ....
    tim-oak
    @tim-oak
    I don't have any
    /var/rudder/configuration-repository/techniques/user_techniques
    Vincent Membré
    @VinceMacBuche
    ncf_techniques ?
    sorry
    tim-oak
    @tim-oak
    in nf_techniques there is a folder for each of my user techniques though not all matching exactly the displayed name in the WebGUI. Some have their very old names (renamed in the old 5.x instance before I export/imorted them ... camelCase instead of under_score_seperated) and the one that caused the problem is prob one of those ...
    tim-oak
    @tim-oak
    the bundle name in technique.cf though is the old original (camelCase) like the name of the directory just the display name and the "# @name .." line in the technique.cf has changed to the under_score_delimited version
    Vincent Membré
    @VinceMacBuche
    What is the content of the technique.cf file ? I think it's broken and you may need to delete it and then reimport it
    tim-oak
    @tim-oak
    ... okay I'try .
    Vincent Membré
    @VinceMacBuche
    I can't reproduce the error message you have
    you can send in private the error message if you want
    or the technique.cf content
    tim-oak
    @tim-oak
    error message is just the I wrote above, I'll send you the technique.cf
    in a min ...
    tim-oak
    @tim-oak
    @VinceMacBuche : send you the techniques I suspect I have broken ...
    tim-oak
    @tim-oak
    uhmm and I see another problem.
    I deleted the directive that used the technique and than the technique.
    verified in the filesystem, folder is gone.
    regenerated policies,
    but the name of the technique shows still up in the "Active tree" on the left side
    "Reference Technique library" ... and error still keep poping up when I open the technique editor
    Francois Armand
    @fanf
    @tim-oak I think you are hit by: https://issues.rudder.io/issues/14288
    deleting the technique in technique editor doesn't delete its reference in directive lib, even if not used. You need to delete it by hand in "setting > active tree" screen.
    (and we really need to work on that one, it's horrible UX for new users :( )
    tim-oak
    @tim-oak
    ... I event can't delete it by hand in the active tree.
    when I click on it it shows the parameter name this technique used, nothing else.
    the technique above I could delete.
    I'll go and purge/reinstall rudder server reimport the techniques and copy back the shared-files ... not that a big deal in this case ;-)
    Francois Armand
    @fanf
    @tim-oak you should always be able to delete it - can you please make a screenshot / open a ticket ?
    we can't let someone in your kind of situation, there must a path to repair a broken state - always
    deleting the faulty technique in last ressort must be possible
    Vincent Membré
    @VinceMacBuche
    do you have a technique at the root of your techniques : /var/rudder/configuration-repository/techniques ? with the id of your cloned technique ?
    tim-oak
    @tim-oak
    sorry - gone already ... the ghost technique was under "Active tree" --> "Reference Techinique library" --> "User techniques"
    I tried to find it in the filesystem tree (egrep -HnRi ...) but couldn't ...
    Anyway next time I manage to break it I'll create a bug report for it - it's probably nothing anyone does easily anyhow.
    tim-oak
    @tim-oak

    sorry to be a PainInTheNeck ;-) but I stumbled over an issue that I thought was resolved in 5.x but seems to has resurfaced. Before opening maybe a bug report let me get me a short feed back here:

    I have a simple technique for setting sysctl variables.
    the technique has two parameters: variable_name and variable_value
    it then checks the "File key-value present" for this pair and on the condition
    file_key_value_present__etc_sysctl_conf_repaired
    it shall "Command execution" /sbin/sysctl -p

    Now I can instantiate different var/val through the directives.

    But in the compliance report all but the first execution of the command have a message status of "missing".

    Anything I can do about that?
    In "settings" --> "general" --> "unexpected reports interpretation"
    I tried both: "Ignore duplicated compliance report" and Don't ignore,
    "Allows multiple reports for configuration based on multivalued variable" is ON...

    Nicolas Charles
    @ncharles
    it's because only one execution of command is made most probably
    good news is: we do have a sysctl method now
    tim-oak
    @tim-oak

    Ah ;-) Good news indeed.
    Where is that? Can't see it under Directives? (in 6.0.4 ?)

    I had the same technique under 5.x and there it worked ...

    Francois Armand
    @fanf
    @tim-oak it should not be worse than in 5.0. If it is, it's a regression and regression are forbiden. Would you mind opening a tickeT?
    tim-oak
    @tim-oak
    I will,
    my 5.x instance is still running so I can compare both situations again.
    Nicolas Charles
    @ncharles
    it's a generic method, called sysctl_value
    tim-oak
    @tim-oak
    @fanf: created #17004
    @ncharles : so this method will probably also be in 6.0.5 ?
    Nicolas Charles
    @ncharles
    it will be yes
    tim-oak
    @tim-oak
    :+1: