Problem running "mantis onboard -o example -t example.com" like in setup video

[liquidberny]

I'm running mantis on Ubuntu 24.04 LTS x86_64 in a virtual machine, did everything following the setup instructions, had to install docker using the apt repository following these instructions.

And following this video as a guide, so I prompted sudo su, entered ./docker-setup-ubuntu.sh and used this prompt as a test: mantis onboard -o example -t example.com

This is the response output:

[2024-07-04 20:50:03,300] --> INFO: MANTIS ASSET DISCOVERY - STARTED
[2024-07-04 20:50:03,301] --> INFO: Executing workname workflowName='default' schedule='daily between 00:00 and 04:00' cmd=[] scanNewOnly=False workflowConfig=[Module(moduleName='discovery', tools=['Subfinder', 'Amass'], order=1), Module(moduleName='prerecon', tools=['FindCDN', 'Naabu'], order=2), Module(moduleName='activehostscan', tools=['HTTPX_Active', 'HTTPX'], order=3), Module(moduleName='activerecon', tools=['Wafw00f'], order=4), Module(moduleName='scan', tools=['DNSTwister', 'Nuclei', 'Corsy'], order=5), Module(moduleName='secretscanner', tools=['SecretScanner'], order=6)]
[2024-07-04 20:50:03,321] --> INFO: Inserting user input into database
Traceback (most recent call last):
  File "/home/mantis/launch.py", line 29, in <module>
    main()
  File "/home/mantis/launch.py", line 23, in main
    MantisWorkflow.select_workflow(args=args)
  File "/home/mantis/mantis/workflows/mantis_workflow.py", line 9, in select_workflow
    asyncio.run(Workflow.workflow_executor(args))
  File "/usr/local/lib/python3.9/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete
    return future.result()
  File "/home/mantis/mantis/modules/workflow.py", line 62, in workflow_executor
    await CrudUtils.insert_assets(assets=asset_dict_list, source='internal')
  File "/home/mantis/mantis/utils/crud_utils.py", line 73, in insert_assets
    await add_assets_query(asset_data=asset_list)
  File "/home/mantis/mantis/db/crud_assets.py", line 7, in add_assets_query
    asset = await assets_collection.insert_many(asset_data, False) # 'ordered': "false"}
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.9/site-packages/pymongo/_csot.py", line 105, in csot_wrapper
    return func(self, *args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/pymongo/collection.py", line 707, in insert_many
    blk.execute(write_concern, session=session)
  File "/usr/local/lib/python3.9/site-packages/pymongo/bulk.py", line 513, in execute
    return self.execute_command(generator, write_concern, session)
  File "/usr/local/lib/python3.9/site-packages/pymongo/bulk.py", line 390, in execute_command
    with client._tmp_session(session) as s:
  File "/usr/local/lib/python3.9/contextlib.py", line 119, in __enter__
    return next(self.gen)
  File "/usr/local/lib/python3.9/site-packages/pymongo/mongo_client.py", line 1729, in _tmp_session
    s = self._ensure_session(session)
  File "/usr/local/lib/python3.9/site-packages/pymongo/mongo_client.py", line 1712, in _ensure_session
    return self.__start_session(True, causal_consistency=False)
  File "/usr/local/lib/python3.9/site-packages/pymongo/mongo_client.py", line 1657, in __start_session
    self._topology._check_implicit_session_support()
  File "/usr/local/lib/python3.9/site-packages/pymongo/topology.py", line 538, in _check_implicit_session_support
    self._check_session_support()
  File "/usr/local/lib/python3.9/site-packages/pymongo/topology.py", line 554, in _check_session_support
    self._select_servers_loop(
  File "/usr/local/lib/python3.9/site-packages/pymongo/topology.py", line 238, in _select_servers_loop
    raise ServerSelectionTimeoutError(
pymongo.errors.ServerSelectionTimeoutError: mantis.db:27017: [Errno 113] No route to host, Timeout: 30s, Topology Description: <TopologyDescription id: 66870afb91af2a1356b57861, topology_type: Unknown, servers: [<ServerDescription ('mantis.db', 27017) server_type: Unknown, rtt: None, error=AutoReconnect('mantis.db:27017: [Errno 113] No route to host')>]>

[Ncoder2]

Hi @liquidberny , the error occurs when you mantis cli is not able to push data to mongodb.
The setup file spins mantis cli, appsmith and mongodb docker and assigns this IP to mongodb and adds it etc/hosts
sudo -- sh -c -e "echo '10.10.0.3 mantis.db' >> /etc/hosts";

Please re-run the installation script and check the below:

1. Choose YES when asked "sudo is required for running docker and adding aliases/commands on host system ${NC}"
2. Also, choose OPTION 1 again when you re-install, "Delete all the previously created containers"
3. Check the status of the running containers at the end of the script

• If the docker fails to start:
  - Check if you have the latest version of docker and docker compose. This is the command "docker compose up " we use, some versions have docker-compose etc.

4. Check your etc/hosts if the entry of db is added.
5. The installation script will finally show the status of all the containers, that should all be up and running and the script should provide this message "Mantis has been setup successfully on docker!", if installation was successful

Do paste the installation logs in case there are any issues,along with OS version etc.

[liquidberny]

Hi @Ncoder2 thank you for responding, I've followed steps from 1 to 3 and using the command docker compose up shows something about mongo:

mongodb           | 
mongodb           | WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!
mongodb           |   see https://jira.mongodb.org/browse/SERVER-54407
mongodb           |   see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2
mongodb           |   see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814
mongodb           | 
mongodb           | /usr/local/bin/docker-entrypoint.sh: line 416:    26 Illegal instruction     (core dumped) "${mongodHackedArgs[@]}" --fork

Could be this the actual issue? I'll check how to add AVX support to my current virual machine but if you have any information on this I would appreciate if you share it with me.

using docker ps -a shows this output:

CONTAINER ID   IMAGE                                     COMMAND                  CREATED          STATUS                            PORTS                                       NAMES
d4bf135ab546   appsmith/appsmith-ce                      "/opt/appsmith/entry…"   13 minutes ago   Restarting (132) 29 seconds ago                                               appsmith
beb12bbba5cc   ghcr.io/phonepe/mantis:latest             "sleep infinity"         13 minutes ago   Up 13 minutes                                                                 mantis
90b3f580c439   mongo:latest                              "docker-entrypoint.s…"   13 minutes ago   Restarting (132) 22 seconds ago                                               mongodb
4d571fdaf24e   ghcr.io/phonepe/mantis-dashboard:latest   "/bin/sh -c 'uvicorn…"   32 minutes ago   Up 15 minutes                     0.0.0.0:8000->8000/tcp, :::8000->8000/tcp   mantis-dashboard

Respecting point 4:

127.0.0.1 localhost
127.0.1.1 osint

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
10.10.0.3  mantis.db
127.0.0.1  mantis.dashboard

Launching the scripts keeps showing the same error.

[liquidberny]

I got mantis installed on WSL instead of Ubuntu on Oracle VM and it worked just fine, the issue had something to do with AVX support on Oracle VM.

[Ncoder2]

Great ! Thanks for recording this @liquidberny !