Gvmd 26.35.0 crashes after scan reaches Done – column "severity_error" does not exist → task set to Interrupted

Environment

Problem

Scans complete successfully on the scanner side and reach status Done, but immediately afterward gvmd aborts and the task is changed to Interrupted.

Relevant gvmd log excerpt:

event task:MESSAGE:... Status of task ... has changed to Processing
event task:MESSAGE:... Status of task ... has changed to Done
event alert:MESSAGE:... The alert nvas CSV was triggered (Event: Task status changed to 'Done', Condition: Always)

md manage:WARNING:... sql_exec_internal: PQexec failed: ERROR:  column "severity_error" does not exist
LINE 1: ...t) FROM results WHERE report = 45 AND severity != SEVERITY_E...
^
(7)
md manage:WARNING:... sql_exec_internal: SQL: SELECT count (DISTINCT nvt) FROM results WHERE report = 45 AND severity != SEVERITY_ERROR;
md manage:WARNING:... sql_x: sql_exec_internal failed

... backtrace ...

md manage:MESSAGE:... Received Aborted signal
md manage:WARNING:... manage_cleanup_process_error: Error exit, setting running task to Interrupted

ospd-openvas logs show the scan finishing normally (“Host scan finished” / “Scan finished”). No blocks or interference from CrowdStrike Falcon (nothing in the Falcon console).

Analysis

The scan itself finishes correctly. The failure occurs in post-processing (result counting / alert path). The SQL sent to PostgreSQL contains the literal string SEVERITY_ERROR instead of the expanded numeric constant. This causes the query to fail, gvmd aborts, and the task is forced to Interrupted.

Questions

  • Is this a known issue in gvmd 26.35.0 / DB revision 280?
  • Is there a workaround (other than disabling the alert that triggers on Done)?
  • Should a GitHub issue be opened against gvmd?

Happy to provide additional logs or test any suggested fixes.

1 Like

@ChanScan

This looks like the wrong database version. Are you sure you’re running the latest containers? I’m no Docker expert myself, but :slightly_smiling_face:

Eero

For SQL relevant errors usually the best, in this case one already exists:

Fixed with fix: include severity constant in report SQL by ozgen · Pull Request #3077 · greenbone/gvmd · GitHub and Release gvmd 26.36.0 · greenbone/gvmd · GitHub

4 Likes