MongoDB startup issues

MongoDB since version 5 requires AVX support from the CPU. Certain virtualized environments don’t support AVX instructions. We strongly recommend contacting your cloud provider to enable AVX support for the virtual machine, but if it’s not possible, a workaround for this is to pin MongoDB to version 4 in docker-compose.yaml. Below are logs which you might see when this is the case:

artemis-backend-1  |   File "/usr/local/lib/python3.11/site-packages/pymongo/", line 238, in _select_servers_loop
artemis-backend-1  |     raise ServerSelectionTimeoutError(
artemis-backend-1  | pymongo.errors.ServerSelectionTimeoutError: db:27017: [Errno -2] Name does not resolve, Timeout: 30s, Topology Description: <TopologyDescription id: 64171dc4adf6cec1ffeb07db, topology_type: Unknown, servers: [<ServerDescription ('db', 27017) server_type: Unknown, rtt: None, error=AutoReconnect('db:27017: [Errno -2] Name does not resolve')>]>
artemis-db-1  |
artemis-db-1  | WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!
artemis-db-1  |   see
artemis-db-1  |   see also
artemis-db-1  |   see also
artemis-db-1  |
artemis-db-1  | /usr/local/bin/ line 416:    26 Illegal instruction     "${mongodHackedArgs[@]}" --fork

Shodan module startup issues

If you see the following error in the logs:

artemis-shodan-vulns-1  |   File "/opt/artemis/modules/", line 97, in <module>
artemis-shodan-vulns-1  |     raise Exception("Shodan API key is required")
artemis-shodan-vulns-1  | Exception: Shodan API key is required

That means the Shodan module wasn’t able to start because an API key was not configured. To fix this, provide the SHODAN_API_KEY configuration variable, see Configuration options.