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
    @binibitobi_gitlab just to be sure, what version of rudder ? And do you use package technique or something else ?
    peckpeck
    @peckpeck
    @binibitobi_gitlab rudder checks with the package manager, but it keep a cache of available package to avoid doing yum update all the time
    Benjamin Dupalut
    @binibitobi_gitlab
    Rudder 6.2.1 and yes I use the package technique.
    peckpeck
    @peckpeck
    the default cache time is 6h IIRC
    Benjamin Dupalut
    @binibitobi_gitlab
    @peckpeck Is it trying to compare the latest available version to the installed version or is it checking if an update is available?
    peckpeck
    @peckpeck
    the cache is in /var/rudder/cfengine-community/state/packagesupdates*
    it is comparing currently installed version with last available version in the cache
    cache taken from the yum index
    Benjamin Dupalut
    @binibitobi_gitlab
    OK, thanks. So I'm surely going to have a problem with my disabled repository?
    peckpeck
    @peckpeck
    until the cache is refreshed
    you could force a cache refreshby removing it
    Benjamin Dupalut
    @binibitobi_gitlab
    rm /var/rudder/cfengine-community/state/packages_updates* ?
    I still have an error on rudder. Since the repository is disabled when rudder builds his cache, is it "normal" that he doesn't see the latest version available?
    Nicolas Charles
    @ncharles
    yes, Rudder agent only knows what the repositories tell
    the command to check if packages are up do date is with yum check-updates
    Nicolas Charles
    @ncharles
    code for package module is in /var/rudder/ncf/common/10_ncf_internals/modules/packages/yum
    if you really want to clear all packages caches, you should rm /var/rudder/cfengine-community/state/packages*
    Benjamin Dupalut
    @binibitobi_gitlab

    Hello,

    I enabled the repository and deleted the cache via rm /var/rudder/cfengine-community/state/packages*. I ran a rudder agent run and still have a non-compliant return.

    How can I investigate this problem? Can I open the cache files to check which version rudder considers the latest?

    Benjamin Dupalut
    @binibitobi_gitlab
    Hello @ncharles @peckpeck @fanf,
    Any idea ?
    Francois Armand
    @fanf
    @binibitobi_gitlab : @fdall is trying to reproduce to know what is happening
    Benjamin Dupalut
    @binibitobi_gitlab
    @fanf Great, thank you. Tell me if I can provide any info or do some testing to help.
    Fdall
    @Fdall

    @binibitobi_gitlab If you really want to see what the agent is seeing (outside of cache), you can call the packages api yourself. For instance try to run on your agent:

    /var/rudder/cfengine-community/modules/packages/yum list-installed < /dev/null | grep -A3 burp

    This will give you the installed version seen by the API, without any cache involved. If you want to see which packages are available for update via the api try:

    /var/rudder/cfengine-community/modules/packages/yum list-updates < /dev/null
    Try to compare the version with the one you are expecting. check if the burp package appears in the "list updates" output. If it doesn't, it is most likely a cache issue
    Benjamin Dupalut
    @binibitobi_gitlab
    With the epel/x86_64 repository enabled or not, the command /var/rudder/cfengine-community/modules/packages/yum list-updates < /dev/null | grep burp gives me no results.
    However, the rudder server still shows me non-compliant.
    Fdall
    @Fdall
    What version did the first command output?
    Benjamin Dupalut
    @binibitobi_gitlab
    /var/rudder/cfengine-community/modules/packages/yum list-installed < /dev/null | grep -A3 burp
    Name=burp-client
    Version=2.1.32-1.el7
    Architecture=x86_64
    Fdall
    @Fdall
    Does the output of rudder agent run -i show any information on the error?
    Nicolas Charles
    @ncharles
    are you trying to install "burp" or "burp-client" ?
    Benjamin Dupalut
    @binibitobi_gitlab
    burp-client
    taavit21
    @taavit21
    Hello, i have this problem ever since i upgraded to rudder server 6.2 that when i click on agent version the query comes up empty
    Francois Armand
    @fanf
    hello @taavit21 , thanks for reporting. I think it is https://issues.rudder.io/issues/18791, and somehow its correction slipped in past patch version
    sorry about that!
    Nicolas Charles
    @ncharles
    @binibitobi_gitlab if you rudder agent run -I, does it tell you why it assumes it's not compliant ?
    Benjamin Dupalut
    @binibitobi_gitlab

    @ncharles Following your remark on the difference between the burp and burp-client packages, I checked my directive and I test the presence of the burp package and not burp-client. I added a directive for the burp-client package and there the feedback on rudder is OK.

    However, on my other servers (Debian), rudder returns "OK" for the directive with the burp package.

    Why doesn't it show me 'non-compliant' like the server under CentOS?

    Vincent Membré
    @VinceMacBuche
    is burd the name of the package on CentOS ? you need to put the real package name, like here burp-client
    Benjamin Dupalut
    @binibitobi_gitlab

    In Centos and under Debian, the package is called burp-client. My directive tested the burp package and therefore had a 'non-compliant' coherent return for my CentOS server.

    For cons, I do not understand why rudder showed me a return 'compliant' for my Debian servers with the burp packet directive.

    Fdall
    @Fdall
    @binibitobi_gitlab I believe it comes from how the package managers are handling meta-packages and aliases
    Benjamin Dupalut
    @binibitobi_gitlab
    @Fdall To be sure I understood correctly, APT would consider that my burp directive matches to the burp-client package but not yum?
    Nicolas Charles
    @ncharles
    that's possible
    vim can be installed by apt install vim, but yum install vim-enhanced
    Benjamin Dupalut
    @binibitobi_gitlab
    Ok, thank you very much for your help @Fdall @ncharles @peckpeck @Fdall .
    On another topic, how do I know which plugins are open-source in this list ?
    Alexis Mousset
    @amousset
    You can access free plugins at https://repository.rudder.io/plugins/6.2/
    Benjamin Dupalut
    @binibitobi_gitlab
    So a plugin that isn't on this page isn't open-source?
    I requested a quote on your site. Do you have an idea of the response time of the sales department?
    Francois Armand
    @fanf
    @binibitobi_gitlab you will be contacted tomorrow
    Benjamin Dupalut
    @binibitobi_gitlab
    Great, thank you.
    Francois Armand
    @fanf
    @binibitobi_gitlab open source plugins have their sources here: https://github.com/Normation/rudder-plugins/