helm-charts icon indicating copy to clipboard operation
helm-charts copied to clipboard

time="2025-07-25T07:26:50Z" level=fatal msg="crowdsec init: while initializing LAPIClient: authenticate watcher (crowdsec-agent-qw9s5): API error: ent: machine not found"

Open urbaman opened this issue 9 months ago • 3 comments

Hi,

Using latest helm chart:

helm list -n crowdsec
NAME            NAMESPACE       REVISION        UPDATED                                         STATUS          CHART           APP VERSION
crowdsec        crowdsec        4               2025-07-25 09:23:41.958593162 +0200 CEST        deployed        crowdsec-0.19.5 v1.6.10
helm upgrade -i crowdsec crowdsec/crowdsec -f crowdsec-values.yaml -n crowdsec --create-namespace
Release "crowdsec" has been upgraded. Happy Helming!
NAME: crowdsec
LAST DEPLOYED: Fri Jul 25 09:23:41 2025
NAMESPACE: crowdsec
STATUS: deployed
REVISION: 4
NOTES:
Thank you for installing crowdsec.
## Local API URL
http://crowdsec-service:8080


The default credentials are :
login : [email protected]
password : <password>

Please update the password when you connect to metabase for the first time.

Since today or so, agent pods stuck in CrashBackLoopOff with the following error:

time="2025-07-25T07:26:50Z" level=fatal msg="crowdsec init: while initializing LAPIClient: authenticate watcher (crowdsec-agent-qw9s5): API error: ent: machine not found"

Is there a way to solve?

urbaman avatar Jul 25 '25 07:07 urbaman

@urbaman: Thanks for opening an issue, it is currently awaiting triage.

If you haven't already, please provide the following information:

  • kind : bug, enhancementor documentation
  • area : agent, appsec, configuration, cscli, local-api

In the meantime, you can:

  1. Check Crowdsec Documentation to see if your issue can be self resolved.
  2. You can also join our Discord.
  3. Check Releases to make sure your agent is on the latest version.
Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the forked project rr404/oss-governance-bot repository.

github-actions[bot] avatar Jul 25 '25 07:07 github-actions[bot]

@urbaman: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.

  • /kind bug
  • /kind documentation
  • /kind enhancement
Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the forked project rr404/oss-governance-bot repository.

github-actions[bot] avatar Jul 25 '25 07:07 github-actions[bot]

Hi,

I had to delete and re-deploy the chart, probably due to persistent volumes? Is there a proper guide to upgrade and persistence volumes?

Thank you.

urbaman avatar Jul 25 '25 07:07 urbaman