Visitar URL original
Runners - Reconmap docs
Skip to content

Runners

Runners are the machines where Reconmap executes commands. You can see and manage them by navigating to Settings > Runners in the dashboard.

Runners list

The list shows every registered runner with its status (Online if it pinged the API in the last 5 minutes, Offline otherwise), its name, hostname, operating system, architecture, CPU, memory, IP address, listen address, and the last boot and ping times.

Use the Refresh button to reload the list on demand, without reloading the page.

Adding a runner

Click New runner on the list page to open the New runner dialog. Enter a name, the hostname, and the listen address, then click Save.

When the runner is created, its client ID and client secret are displayed in the dialog. They are only shown once, so copy them before closing it. Use them to configure the runner.

Runner details

Click a runner's name to open its details page. It shows every detail the runner has reported:

  • ID, client ID and whether the runner is enabled.
  • Version, hostname, operating system, architecture, CPU and memory.
  • IP address and listen address.
  • When the runner last booted and last pinged the API.

Empty values are shown as (empty), which usually means the runner has not reported that detail yet.

Users with the administrator or superuser role can also open a terminal on the runner from the details page. See Runner terminal security before enabling this in production.

Running scans

Runners poll the API for scheduled commands. For scans started from Run scan, a runner executes the stored command line, reports each task as running, succeeded or failed, and then uploads the command output (standard output, or the usage's output file from the runner's working directory) to Reconmap so it is parsed into the scan's project. The runner needs the scanning tools (for example nmap, testssl, shcheck.py) installed and on its PATH; a missing tool shows up as a failed task with the error. Tools that write to a file use a fixed name in the working directory, so avoid running two scans that use the same file name at the same time.