mipo

No Scanner

A scan job is assigned to a scanner_id that no longer exists in the scanners table. Most common cause: an operator deleted the scanner while it still had outstanding jobs.

How to

Investigate

  1. Open Health > Job Errors and filter class = no_scanner
  2. Note the missing scanner ID(s) in the context column
  3. Check Audit > Auth + Audit > Changes for who deleted the scanner and when

Repair

  1. For non-essential jobs: bulk-fail (terminal)
  2. For important jobs: select rows, click Triage, choose Reassign, pick a live scanner
  3. Verify the chosen scanner is active and heartbeating

Gotchas

  • Reassigning to a disabled scanner just defers the problem — pick an active scanner.
  • Deleted scanners cannot be recovered. Delete with care; consider Disable instead.
  • A scan with many no_scanner jobs may have lost ALL its scanner — operator deleted in a bulk action.

API calls (3)

MethodPathDescription
GET /api/health/job-errors?errorClass=no_scanner List active rows
POST /api/health/job-errors/:stateId/repair Apply fail or reassign
POST /api/health/job-errors/bulk-repair Bulk apply

Related