Closed modem7 closed 1 year ago
@modem7: Thanks for opening an issue, it is currently awaiting triage.
In the meantime, you can:
Hello,
Thanks for the report, we are looking into it.
What version did you have before ? The install log says it was already partially installed.
(Didn't manage to reproduce on ubuntu 20)
Edit: didn't manage to reproduce on ubuntu 22.04 from 1.4.6 using the same aptitude commands
Hello,
Thanks for the report, we are looking into it.
What version did you have before ? The install log says it was already partially installed.
(Didn't manage to reproduce on ubuntu 20)
Edit: didn't manage to reproduce on ubuntu 22.04 from 1.4.6 using the same aptitude commands
Heya
❯ sudo cscli version
2023/05/16 23:36:30 version: v1.4.6-debian-pragmatic-5f71037b40c498045e1b59923504469e2b8d0140
2023/05/16 23:36:30 Codename: alphaga
2023/05/16 23:36:30 BuildDate: 2023-02-09_14:33:16
2023/05/16 23:36:30 GoVersion: 1.19.2
2023/05/16 23:36:30 Platform: linux
2023/05/16 23:36:30 Constraint_parser: >= 1.0, <= 2.0
2023/05/16 23:36:30 Constraint_scenario: >= 1.0, < 3.0
2023/05/16 23:36:30 Constraint_api: v1
2023/05/16 23:36:30 Constraint_acquis: >= 1.0, < 2.0
Cheers!
Will close this for now.
After a VM restore and crowdsec reinstall, it seems to have behaved again. No idea why this occurred in first place, however.
What happened?
What did you expect to happen?
Crowdsec to update normally
How can we reproduce it (as minimally and precisely as possible)?
sudo aptitude update && sudo aptitude safe-upgrade -y
Anything else we need to know?
No response
Crowdsec version
OS version
Enabled collections and parsers
Acquisition config
Config show
Prometheus metrics
Related custom configs versions (if applicable) : notification plugins, custom scenarios, parsers etc.