This tomcat process is rather old and not needed, so I killed him manually and crowdesc service startet without problems in the past and i could also see decisions/blocked hosts, etc… - everything working fine.
I have the impression that with the last cowdsec update, this does not work any more!
When killing the tomcat process on port 8080, I can start crowdsec service but when fetching the decisions list with cscli decisions list the system needs a lot of time to respond and then tells me:
Unable to list decisions : performing request: Get "http://127.0.0.1:8080/v1/alerts?has_active_decision=true&include_capi=false&limit=100": could not get jwt token: Post "http://127.0.0.1:8080/v1/watchers/login": EOF
After that, the corwdsec service died and is not running any more!
The firewall settings (ufw) did not change - port 8080 is reachable/open. I do not have any idea, why the system is not wrking any more.
Well, I am not sure on which port crowdsec is running. The default port I guess. It was never changed. When trying cscli decisions list it tries http://127.0.0.1:8080 (see above), so I guess it is running on port 8080.
Crowdsec service is running, but dies/stops after trying cscli decisions list.