Hello everyone,
I am still relatively new to OpenVAS and after the first successful scans and an update of OpenVAS, it no longer starts with the following messages:
Job for gvmd.service failed because a timeout was exceeded.
See “systemctl status gvmd.service” and “journalctl -xeu gvmd.service” for details.
systemctl status gvmd.service
Apr 04 11:25:43 ThinkPad-T480 systemd[1]: gvmd.service: Can’t open PID file ‘/run/gvmd/gvmd.pid’ (yet?) after start: No such file or directory
Apr 04 11:25:43 ThinkPad-T480 gvmd[400911]: md manage:MESSAGE:2025-04-04 09h25.43 utc:400911: check_db_versions: database version of database: 256
Apr 04 11:25:43 ThinkPad-T480 gvmd[400911]: md manage:MESSAGE:2025-04-04 09h25.43 utc:400911: check_db_versions: database version supported by manager: 258
Apr 04 11:25:43 ThinkPad-T480 gvmd[400911]: md main:CRITICAL:2025-04-04 09h25.43 utc:400911: gvmd: database is wrong version
Apr 04 11:25:43 ThinkPad-T480 gvmd[400911]: md main:CRITICAL:2025-04-04 09h25.43 utc:400911: gvmd: Your database is too old for this version of gvmd.
Apr 04 11:25:43 ThinkPad-T480 gvmd[400911]: md main:CRITICAL:2025-04-04 09h25.43 utc:400911: gvmd: Please migrate to the current data model.
Apr 04 11:25:43 ThinkPad-T480 gvmd[400911]: md main:CRITICAL:2025-04-04 09h25.43 utc:400911: gvmd: Use a command like this: gvmd –migrate
gvmd --migrate
(gvmd:404056): md manage-WARNING **: 11:31:46.831: sql_open: PQconnectPoll failed
(gvmd:404056): md manage-WARNING **: 11:31:46.831: sql_open: PQerrorMessage (conn): connection to server on socket “/var/run/postgresql/.s.PGSQL.5432” failed: FATAL: Rolle »######« existiert nicht
(gvmd:404056): md manage-WARNING **: 11:31:46.831: init_manage_open_db: sql_open failed
journalctl -xeu gvmd.service
Apr 04 11:34:46 ThinkPad-T480 systemd[1]: gvmd.service: Scheduled restart job, restart counter is at 537.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ Automatic restarting of the unit gvmd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Apr 04 11:34:46 ThinkPad-T480 systemd[1]: Starting gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)…
░░ Subject: A start job for unit gvmd.service has begun execution
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ A start job for unit gvmd.service has begun execution.
░░
░░ The job identifier is 78818.
Apr 04 11:34:46 ThinkPad-T480 gvmd[405561]: md main:MESSAGE:2025-04-04 09h34.46 utc:405561: Greenbone Vulnerability Manager version 25.1.3 (DB revision 258)
Apr 04 11:34:46 ThinkPad-T480 systemd[1]: gvmd.service: Can’t open PID file ‘/run/gvmd/gvmd.pid’ (yet?) after start: No such file or directory
Apr 04 11:34:46 ThinkPad-T480 gvmd[405563]: md manage:MESSAGE:2025-04-04 09h34.46 utc:405563: check_db_versions: database version of database: 256
Apr 04 11:34:46 ThinkPad-T480 gvmd[405563]: md manage:MESSAGE:2025-04-04 09h34.46 utc:405563: check_db_versions: database version supported by manager: 258
Apr 04 11:34:46 ThinkPad-T480 gvmd[405563]: md main:CRITICAL:2025-04-04 09h34.46 utc:405563: gvmd: database is wrong version
Apr 04 11:34:46 ThinkPad-T480 gvmd[405563]: md main:CRITICAL:2025-04-04 09h34.46 utc:405563: gvmd: Your database is too old for this version of gvmd.
Apr 04 11:34:46 ThinkPad-T480 gvmd[405563]: md main:CRITICAL:2025-04-04 09h34.46 utc:405563: gvmd: Please migrate to the current data model.
Apr 04 11:34:46 ThinkPad-T480 gvmd[405563]: md main:CRITICAL:2025-04-04 09h34.46 utc:405563: gvmd: Use a command like this: gvmd --migrate
lines 2903-2925/2925 (END)
Does anyone know this problem and is there a solution?
Since this problem came with an update of OpenVAS, I suspect that I will get this problem again and again…
I hope you can help me.
Many thanks and best regards