You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I set up the test environment to test a collection, but couldn't get it to work.
Got message FATA unable to load hubtest: path to crowdsec binary 'crowdsec' doesn't exist or is not in $PATH, can't run
Although I have added the related path to variable PATH
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 BirthdayResearch/oss-governance-bot repository.
cscli hubtest supports --crowdsec which is a string which points to the crowdsec binary by default its crowdsec which attempts to find it via the PATH options but you can provide /path/to/bin/crowdsec as an override.
Edit: however, its a mess really cause you have this issue #3182 which means you will have to do this
Then within the hub directory it cannot find cscli or crowdsec so you would have to run this:
root@bookworm:/tmp/tmp.hdn3hnsCvq/crowdsec-v1.6.4/tests/hub# csdev hubtest --cscli "$(dirname $PWD)/cscli" --crowdsec "$(dirname $PWD)/crowdsec" run --all
INFO Running test 'CVE-2017-9841'
Not to also mention that csdev alias can also hit issues when not running inside the test directory so you should update the dev.yaml to have full paths instead of having ./ with sed:
root@bookworm:/tmp/tmp.hdn3hnsCvq/crowdsec-v1.6.4/tests# sed -i "s|\./|$PWD/|g" dev.yaml
What happened?
I set up the test environment to test a collection, but couldn't get it to work.
Got message
FATA unable to load hubtest: path to crowdsec binary 'crowdsec' doesn't exist or is not in $PATH, can't run
Although I have added the related path to variable PATH
What did you expect to happen?
Capacity to test my collection, although I'm not quite sure it might have worked since it relies on docker logs.
How can we reproduce it (as minimally and precisely as possible)?
Install the test environment on Debian and try it.
Anything else we need to know?
No response
Crowdsec version
OS version
Enabled collections and parsers
No response
Acquisition config
On Windows:
C:> Get-Content C:\ProgramData\CrowdSec\config\acquis.yaml
paste output here
Config show
Prometheus metrics
Related custom configs versions (if applicable) : notification plugins, custom scenarios, parsers etc.
The text was updated successfully, but these errors were encountered: