Binary Version Mismatch
A scanner is running a binary version below the platform minimum. Older binaries may be missing protocol features the platform requires.
How to
Update the scanner
- Re-deploy the scanner binary on the host using the latest release
- On next heartbeat the version will be reported and the state will auto-resolve
Reassign or fail (if update is not feasible)
- Reassign jobs to a scanner with the right version
- Or fail the jobs if they are not critical
Gotchas
- A scanner with no version reported (NULL) is treated as below minimum — usually means it never heartbeated successfully.
- The minimum version is configured at MIN_SCANNER_VERSION in shared/business-rules/jobErrorRules.ts. Bumping it forces fleet-wide re-deploy.
API calls (1)
| Method | Path | Description |
|---|---|---|
| POST | /api/health/job-errors/:stateId/repair | action=fail | reassign |
Related
- Job Errors Overview — Category model
- Scanners — See per-scanner version