Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Crystian Geovani Dorabiatto
    @cdorabiatto

    Good night, how are you? Im getting this error on rudder agent, Could you please help me ?

    Rudder agent 6.2.19-debian8
    Node uuid: f9fd7c0e-9dd1-4002-ab9a-d9e8e89778fb
    error: Failed to establish TLS connection: underlying network error (Connection reset by peer)
    error: No suitable server found
    error: Failed to establish TLS connection: underlying network error ()
    error: No suitable server found
    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: 0.07s

    #
    2 replies
    Elenui
    @Elenui
    Hello Guys I may need ur guidance. One of my node running Deb 11 doesn't send report since I installe it. I check the agent's health it said OK. The cron job run. Tried to run the command every minute without any luck. Tried after this to run the cron command by hand but still nothing. If I trigger my agent everything works.
    38 replies
    any idea ?
    fanf42
    @fanf42:matrix.org
    [m]
    @Elenui rudder agent check should check that, and the cron too, can you open a ticket ?
    Elenui
    @Elenui
    It's an old version do u want it anyway ?
    Tanguy PELADO
    @tpelado

    Hey all,

    Trying to update the rudder agent to 7.1 WITH rudder. I've set the apt source list file to rudder 7.1, however a directive to update the rudder-agent package to the "latest version" doesn't upgrade it to 7.X, as opposed to just doing "apt install rudder-agent". Is this expected behaviour?

    10 replies
    skygeneve
    @skygeneve
    Hello, I have upgraded my server to Debian 11 with python 3.9 and the script rudder.py is not anymore working. Can someone help pls?
    peckpeck
    @peckpeck
    which script are you talking about ?
    skygeneve
    @skygeneve
    rudder.py
    this is used with ansible
    Alexis Mousset
    @amousset:matrix.org
    [m]
    you can try with this version
    wjterveld
    @wjterveld

    Hello All,
    We just did an upgrade from 6.2.19 to 7.0 All seems to be going well but my status has a broken heart with the following errors:

    Cannot build Rule vals;
    cause was: Could not find configuration vals;
    cause was: Cannot find directive with id 'e082ce3f-8a54-47b2-a991-f0ed3212d6e8-distributePolicy' when building rule 'distributePolicy' (e082ce3f-8a54-47b2-a991-f0ed3212d6e8-DP);
    cause was: Cannot find directive with id '7781a875-0636-4343-8219-1b272acb2f22-distributePolicy' when building rule 'distributePolicy' (7781a875-0636-4343-8219-1b272acb2f22-DP);
    cause was: Cannot find directive with id '555267df-9b4e-42c4-93cf-e313f67866ae-distributePolicy' when building rule 'distributePolicy' (555267df-9b4e-42c4-93cf-e313f67866ae-DP);
    cause was: Unexpected: Cannot find directive with id '90175412-aa5c-43aa-85d5-c8a80743cb4a-distributePolicy' when building rule 'distributePolicy' (90175412-aa5c-43aa-85d5-c8a80743cb4a-DP)

    I do not understand what these errors are and ho to fix them?

    When I search the disk for "e082ce3f-8a54-47b2-a991-f0ed3212d6e8" I do see an some old inventories..

    ./var/rudder/inventories/received/idvault02-e082ce3f-8a54-47b2-a991-f0ed3212d6e8.ocs.sign
    ./var/rudder/inventories/received/idvault02-e082ce3f-8a54-47b2-a991-f0ed3212d6e8.ocs
    ./var/rudder/inventories/historical/e082ce3f-8a54-47b2-a991-f0ed3212d6e8
    ./var/rudder/inventories/historical/e082ce3f-8a54-47b2-a991-f0ed3212d6e8/2019-10-22_13:22.12.567

    7 replies
    fanf42
    @fanf42:matrix.org
    [m]
    ok, that should not be linked, we will look at that latter on.
    So. Does the nodes with id e082ce3f-8a54-47b2-a991-f0ed3212d6e8, 7781a875-0636-4343-8219-1b272acb2f22, 555267df-9b4e-42c4-93cf-e313f67866ae, 90175412-aa5c-43aa-85d5-c8a80743cb4a are still managed by rudder ? If not, perhaps the migration script does not managed something correctly here. Also: can you try to trigger a full generation (which clean caches)? Click on 'Status', then "regenerate all policies" ?
    wjterveld
    @wjterveld
    This still gives me the same error.. Is there a way to see the name of the nodes or search for them? It could well be that thesse are old nodes and are not managed any more..
    3 replies
    e082ce3f-8a54-47b2-a991-f0ed3212d6e8 This is indeed an old server that is no longer being managed.. The server has not jet been removed from rudder..
    fanf42
    @fanf42:matrix.org
    [m]
    you can force rudder to try to clean up things with an API call (be careful, it will delete the node if it is currently managed by rudder, you will need to send back an inventory, accept it again, etc to get it back: curl -k -X DELETE -H "X-API-TOKEN: your-api-token" 'https://yourRudder/rudder/api/latest/nodes/e082ce3f-8a54-47b2-a991-f0ed3212d6e8?mode=erase'
    (if that doesn't work, we will need to go deeper, but I would prefer to avoid that)
    wjterveld
    @wjterveld
    I ran the command.. Do I need to regenratete the policies again?
    fanf42
    @fanf42:matrix.org
    [m]
    you need to run it for all of the four nodes. I'm not sure if the regeneration start automatically on that case, you can look if the last regeneration was just now in the status
    (else, yes, trigger it by hand)
    wjterveld
    @wjterveld

    I Ran the commands below, but still the same error...

    curl -k -X DELETE -H "X-API-TOKEN: your-api-token" 'https://172.16.101.110/rudder/api/latest/nodes/e082ce3f-8a54-47b2-a991-f0ed3212d6e8?mode=erase'
    curl -k -X DELETE -H "X-API-TOKEN: your-api-token" 'https://172.16.101.110/rudder/api/latest/nodes/7781a875-0636-4343-8219-1b272acb2f22?mode=erase'
    curl -k -X DELETE -H "X-API-TOKEN: your-api-token" 'https://172.16.101.110/rudder/api/latest/nodes/555267df-9b4e-42c4-93cf-e313f67866ae?mode=erase'
    curl -k -X DELETE -H "X-API-TOKEN: your-api-token" 'https://172.16.101.110/rudder/api/latest/nodes/90175412-aa5c-43aa-85d5-c8a80743cb4a?mode=erase'

    fanf42
    @fanf42:matrix.org
    [m]
    (just to be sure: you changed "your-api-token" by an actually valid api token ?)
    wjterveld
    @wjterveld
    oh duhh!! no.. :-(
    how can I get this API token?
    fanf42
    @fanf42:matrix.org
    [m]
    either in rudder ui, in "administration" menu you have an api account sub menu, or there is a system one but only available from the root server (so first solution is simpler most of the time)
    wjterveld
    @wjterveld
    oke.. there are none in the administration.. I will create one
    done.. regenerating the polies takes much longer now!!
    fanf42
    @fanf42:matrix.org
    [m]
    this may be good
    wjterveld
    @wjterveld
    cool!! I still have one error.. but this seems to be an old agent??
    ⇨ Unexpected: Generation ended but some nodes were in errors: Error while building target configuration node for node '798c933f-0f4f-496a-ab75-083c0f20b9b0' which is one of the target of rules. Ignoring it for the rest of the process
    ⇨ Node ahk-prdidm02.xxxxxxl (798c933f-0f4f-496a-ab75-083c0f20b9b0) has an agent which doesn't support sending compliance reports in HTTPS: Rudder agent only support HTTPS reporting for version >= 6.0. You need to either disable that node (in node details > settings > Node State) or update agent version on that node
    I'll start with the disable optien
    fanf42
    @fanf42:matrix.org
    [m]
    yes, it is an agent which is just too old for 7.0 more secured protocols (actually, 6.x supported both but the old protocol was removed in 7.0)
    just to know: why did you upgraded to 7.0 and 7.1 ? 7.0 is almost EOL (and 7.2 is out early next week, with a much refined UI and other cool things)
    wjterveld
    @wjterveld
    great!! ALL is green again!! Thank you so much..
    reason that I upgraded to 7.0 is this problem I tried 6.2 to 7.1 with this error.. so i tried to go a version lower and lower.. until I ended at 7.0 :-)
    So now I know how to fix it I will upgrade to 7.2 ..
    fanf42
    @fanf42:matrix.org
    [m]
    ah ah ok :)
    wjterveld
    @wjterveld
    great work!! Thanx agian.. I will make a new snapshot of the production and try the upgrade on the production servers!!
    fanf42
    @fanf42:matrix.org
    [m]
    hey, you seems to use rudder since a very very long time since you have pre-6.0 agent. May I ask you since when ?
    wjterveld
    @wjterveld
    Oh I thing for 5 years
    I do see still see an error in the stout file..
    2022-09-23 12:36:18.124:WARN:oejs.session:qtp644345897-13:
    java.lang.IllegalStateException: Not started
    Oh fixed it with a jetty restart I think :D
    fanf42
    @fanf42:matrix.org
    [m]
    wow, 5 years is huge :) We welcome feedbacks, especially from long term users, so don't hesitate (even via private email if you prefer)
    wjterveld
    @wjterveld
    Time seems to fly these day's so the 5 years could be 4 or 6 also :D
    fanf42
    @fanf42:matrix.org
    [m]
    ah ah, I understand.
    wjterveld
    @wjterveld
    We have loved the product form the beginning.
    I will provide feedback more often no problem. using a PM maybe the best way..
    fanf42
    @fanf42:matrix.org
    [m]
    you can contact me at francois@rudder.io, or the dev team is available at rudder@rudder.io (and of course, for general info etc, you can use the contact form on the website)
    for the illegalestateerror: it's nothing. It's an exception that is raised when we stop the java server (restart rudder for ex), and we didn't found a way to hide it. It's extremely frustrating, misleading, but armless
    Fdall
    @Fdall
    @skygeneve could you double check that /usr/bin/env/python exists on the machine from where you are running the ansible cli ? If so, do you have a specific error message?
    skygeneve
    @skygeneve
    @Alexis Mousset, no luck still not working
    @Fdall , here is the error => Inventory script (/home/adminmis/ansible/ansible-tnsnames/rudder.py) had an execution error: ERROR: "Name collision on hosts:
    Unable to parse /home/adminmis/ansible/ansible-tnsnames/rudder.py as an inventory source