Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Alexis Mousset
    @amousset
    @Waccabac_twitter it is indeed missing. Could you open an issue?
    Waccabac
    @Waccabac_twitter
    Yes
    Waccabac
    @Waccabac_twitter
    Nicolas Charles
    @ncharles
    you can use the technique in Normation/rudder-techniques#1621 to fix your issue
    pmg
    @pmg7557_twitter
    Hi All, I come back with "job scheduling" pb (see https://issues.rudder.io/issues/18203) and seem to find similar pb with "cron directive", but I have difficulties to analyse. With "normal cron", to test I setup the next launch the next minute; but with "rudder cron directive" I don't known how to do.I have 3 questions :
    Let's say I setup a rudder cron job to start at t1, what I have to do to be sure that the job should run at t1 in a specific node (rudder agent update and rudder agent run before t1?)
    Let's say I setup a rudder cron job to run hourly, when I'll be sure that the job should have run of a node (after rudder agent upate, rudder agent run and one hour later?)
    In both case, I touch a file to see when the job run, but except this, where can I find the running cron job in the log?
    Thanks in advance.
    pmg
    @pmg7557_twitter
    I have a status error :
    32377fd7-02fd-43d0-aab7-28460a91347b / c37f4a6d-8e11-4888-aa56-dd1e2e95aad2; cause was: Unexpected: Unexpected: Inconsistant policy mode: both audit and enforce applied
    Strange? How can I find the cause?
    pmg
    @pmg7557_twitter
    Status error : solved : disabled / re-enabled some directives by group ... no modification ! ... Really strange ...
    Nicolas Charles
    @ncharles
    Hi. The cron technique edits the /etc/cron.d files
    a cron hat's scheduled to be run every hour will use the prefix 0 * * * * for the job
    a cron hourly will simply be a sript added in /etc/cron.hourly
    pmg
    @pmg7557_twitter
    @ncharles Thanks, in fact, the 'cron pb' was due to the 'status error', policies were note updated, but I have no explanation for the status error ...
    Nicolas Charles
    @ncharles
    if you click on it, you can see the details
    it ought to be self explanatory
    (but sometimes it is not so clear as to why
    pmg
    @pmg7557_twitter
    Hi All, inventory failed on an Ubuntu 20 node (recently updated from 16)
    rudder agent inventory -> Generated inventory has been detected as invalid
    rudder agent inventory -v -> use cde : /usr/bin/perl -I /opt/rudder/lib/perl5 /var/rudder/cfengine-community/inputs/inventory/1.0/test-inventory.pl /var/rudder/tmp/inventory/mail-fcd9b9e1-d87c-4d7b-86b6-e9a9880d7d74.ocs
    -> Dumper.c: loadable library and perl binaries are mismatched (got handshake key 0xdb00080, needed 0xcd00080)
    Any idea to solve this pb? And an explanation?
    Nicolas Charles
    @ncharles
    Hi. There's a similar issue here: https://issues.rudder.io/issues/17997
    do you have old .so files in /opt/rudder/lib/perl5/x86_64-linux-gnu-thread-multi/ ?
    pmg
    @pmg7557_twitter
    @ncharles find /opt/rudder/lib/perl5/x86_64-linux-gnu-thread-multi/ -name *.so
    /opt/rudder/lib/perl5/x86_64-linux-gnu-thread-multi/auto/Sub/Identify/Identify.so
    /opt/rudder/lib/perl5/x86_64-linux-gnu-thread-multi/auto/DateTime/DateTime.so
    /opt/rudder/lib/perl5/x86_64-linux-gnu-thread-multi/auto/Package/Stash/XS/XS.so
    /opt/rudder/lib/perl5/x86_64-linux-gnu-thread-multi/auto/List/Util/Util.so
    /opt/rudder/lib/perl5/x86_64-linux-gnu-thread-multi/auto/Data/Dumper/Dumper.so
    /opt/rudder/lib/perl5/x86_64-linux-gnu-thread-multi/auto/HTML/Parser/Parser.so
    /opt/rudder/lib/perl5/x86_64-linux-gnu-thread-multi/auto/Variable/Magic/Magic.so
    Alexis Mousset
    @amousset
    @pmg7557_twitter what does dpkg -l | grep rudder give?
    pmg
    @pmg7557_twitter
    @amousset
    ii rudder-agent 6.0.9-ubuntu16.04 amd64 Configuration management and audit tool - agent
    Alexis Mousset
    @amousset
    ok, you need to install the ubuntu 20.04 agent
    you Rudder repo config probably needs an update
    pmg
    @pmg7557_twitter
    @ncharles @amousset
    No more pb, I did not change anything!
    Matthew Frost
    @mattronix
    @mattronix
    anyway i can leave a node without keys
    so that when it startups the first time it generates them?
    i want to leave a rudder agent inside the ubuntu iso
    that will start up on first startup
    pmg
    @pmg7557_twitter
    @amousset I upgraded the repo
    deb http://repository.rudder.io/apt/6.0/ bionic main
    and
    dpkg -l | grep rudder
    ii rudder-agent 6.0.9-ubuntu18.04 ....
    Is-it normal to see ubuntu 18 and not 20?
    Alexis Mousset
    @amousset
    yes, because bionic is ubuntu 18.04, 20.04 is focal
    pmg
    @pmg7557_twitter
    @amousset Of course :-)
    It's better now, dpkg -l | grep rudder
    ii rudder-agent 6.0.9-ubuntu20.04 ...
    Thanks
    Nicolas Charles
    @ncharles
    @mattronix yes, you may remove the keys, and you'll need to remove the certificate as well
    let me find its path
    /opt/rudder/etc/ssl/agent.cert
    So to have a node without any keys nor trust:
    rm -f /var/rudder/cfengine-community/ppkeys/* && rm -f/opt/rudder/etc/ssl/agent.cert`
    command rudder agent check will regenerate both
    sadasd4354sad5
    @sadasd4354sad5
    failure: repodata/repomd.xml from Rudder_6.2: [Errno 256] No more mirrors to try.
    http://repository.rudder.io/rpm/6.2/RHEL_7/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
    Rudder server install error on cent os 7
    Nicolas Charles
    @ncharles
    6.2 is not yet released, you should pick 6.1
    norbertoaquino
    @norbertoaquino

    Hi, i remove a server and execute rudder agent reset-factory and rudder agent policy-server myspolicyserver but if i click on "Trigger Agent" on web interface i receive this message:

    error: TRUST FAILED, server presented untrusted key: MD5=441c02957c3496133155500f806894be
    error: Failed to connect to host: HOSTNAME
    error Rudder agent was interrupted during execution by a fatal error
    Run with -i to see log messages.

    Summary

    0 components verified in 1 directives
    This summary is incomplete as the agent was interrupted during execution
    Execution time: 7.63s

    #

    On node rudder agent run it's ok

    How solution???

    Alexis Mousset
    @amousset
    Hi @norbertoaquino, which agent and server version?
    norbertoaquino
    @norbertoaquino
    @amousset 6.1.3 server and agent
    Matthew Frost
    @mattronix
    @ncharles thanks :)
    namen3645
    @namen3645
    rudder info: Failed to connect to server: Connection refused
    rudder info: No server is responding on port: 5309
    rudder info: Unable to establish connection to '34.69.72.245'
    error: No suitable server found
    rudder info: Promise belongs to bundle 'update' in file '/var/rudder/cfengine-community/inputs/promises.cf' near line 73
    rudder info: Failed to connect to server: Connection refused
    rudder info: No server is responding on port: 5309
    rudder info: Unable to establish connection to '34.69.72.245'
    error: No suitable server found
    rudder info: Promise belongs to bundle 'update' in file '/var/rudder/cfengine-community/inputs/promises.cf' near line 81
    R: Initial policies have been successfully downloaded from the policy server
    error Rudder agent was interrupted during execution by a fatal error
    PORT STATE SERVICE
    5309/tcp open unknown
    Nmap done: 1 IP address (1 host up) scanned in 0.39 seconds
    Matthew Frost
    @mattronix
    @namen3645 did you whitelist your hosts
    in the settings of the rudder portal
    image.png
    for example i did this
    but
    0.0.0.0 i would not recommend if your new to rudder always use what you need and ours work over the internet
    norbertoaquino
    @norbertoaquino
    hi ! It's possible change default interval of 8 hours for inventory?
    Eric Renfro
    @erenfro
    Gooooood evening.