Hi Everyone o/ I hope it's the good location, I'm ...
# fleet
a
Hi Everyone o/ I hope it's the good location, I'm just starting with FleetDM and I was wondering why I'm not able to see any "vulnerabilities" software on the host I added and on the logs I can only see
Copy code
level=error ts=2023-12-17T17:14:14.374025303Z component=crons cron=vulnerabilities cron=vulnerabilities msg="analyzing vulnerable software: CPE->CVE" err="1 synchronisation error:\n\tunexpected http response from \"<https://nvd.nist.gov/feed>>
level=error ts=2023-12-17T17:14:14.463206417Z component=crons cron=vulnerabilities cron=vulnerabilities msg="post processing CVEs" err="failed to fetch CentOS packages: failed to fetch packages: no such table: centos_pkgs_fixed_cves"
Is there something I didn't do correctly ? 🤔
g
Greetings @Arnaud, What does your infrastructure look like? and what version of Fleet do you have? NVD retired the way Fleet used to handle the processing on December 15th. This was fixed in 4.41. There might be more than one instance of the Fleet server running and errors look like might have Vulnerability Processing not quite set. Take a look here for setting
current_instance_checks
.
a
Thanks for taking the time to answer @Grant Bilstad Everything is running on docker, on a single server (Ubuntu 22 LTS) :
Copy code
root@server:/home/user# docker ps
CONTAINER ID   IMAGE           COMMAND                  CREATED             STATUS             PORTS                                 NAMES
b0c781673184   fleetdm/fleet   "/usr/bin/fleet serve"   About an hour ago   Up About an hour                                         fleet.service
ab0140cb1622   mysql           "docker-entrypoint.s…"   About an hour ago   Up About an hour   127.0.0.1:3306->3306/tcp, 33060/tcp   fleet-mysql.service
02c1d59adfea   caddy           "caddy run --config …"   About an hour ago   Up About an hour                                         fleet-caddy.service
806f52d13906   eqalpha/keydb   "docker-entrypoint.s…"   About an hour ago   Up About an hour   127.0.0.1:6379->6379/tcp              fleet-redis.service
How can I simply check which version I'm running ? Shall I try to pull a new docker image ? 🤔
It turns out, I assumed that following the docker installation from https://fleetdm.com/docs/deploy/deploy-on-hetzner-cloud would be up to date ... it was obviously VERY outdated (running v. 4.14 ; updating fleet.service for systemd etc ...) seems to works better with latest version