GVM not starting up after upgrade (solved - closed)

Archive Greenbone Community Edition
1

Hi,

The scanner was limiting the results because I had an outdated version, now with gvm 21.4 is not even starting the gvm, all I did was run the command apt-get install gvm and it overwrote, installed and deleted some files and now nothing works, here is the installation log.

Start-Date: 2022-06-04 19:36:46
Commandline: apt-get install gvm
Requested-By: kali (1000)
Install: postgresql-14:amd64 (14.3-1, automatic), libldap-common:amd64 (2.5.11+dfsg-1, automatic), libllvm13:amd64 (1:13.0.1-4, automatic), libldap-2.5-0:amd64 (2.5.11+dfsg-1, automatic), postgresql-c>
Upgrade: gvm:amd64 (21.4.2.0, 21.4.4~kali1), libsasl2-2:amd64 (2.1.27+dfsg-2.1, 2.1.28+dfsg-4), libgvm21:amd64 (21.4.2-2, 21.4.4-1), openvas-scanner:amd64 (21.4.2-1, 21.4.4-1), libsasl2-modules-db:amd>
Remove: python3-ospd:amd64 (21.4.4-1)
End-Date: 2022-06-04 19:42:28

thanks for your help

Update (log file):
─# journalctl -xeu gvmd.service 1 ⨯
Jun 05 10:05:05 kali systemd[1]: gvmd.service: start operation timed out. Terminating.
Jun 05 10:05:05 kali systemd[1]: gvmd.service: Failed with result ‘timeout’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support:
░░
░░ The unit gvmd.service has entered the ‘failed’ state with result ‘timeout’.
Jun 05 10:05:05 kali systemd[1]: Failed to start Greenbone Vulnerability Manager daemon (gvmd).
░░ Subject: A start job for unit gvmd.service has failed
░░ Defined-By: systemd
░░ Support:
░░
░░ A start job for unit gvmd.service has finished with a failure.
░░
░░ The job identifier is 9216 and the job result is failed.
Jun 05 10:05:05 kali systemd[1]: gvmd.service: Consumed 1.265s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support:
░░
░░ The unit gvmd.service completed and consumed the indicated resources.
Jun 05 10:05:05 kali systemd[1]: gvmd.service: Scheduled restart job, restart counter is at 1.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support:
░░
░░ Automatic restarting of the unit gvmd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jun 05 10:05:05 kali systemd[1]: Stopped Greenbone Vulnerability Manager daemon (gvmd).
░░ Subject: A stop job for unit gvmd.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit gvmd.service has finished.
░░
░░ The job identifier is 9353 and the job result is done.
Jun 05 10:05:05 kali systemd[1]: gvmd.service: Consumed 1.265s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit gvmd.service completed and consumed the indicated resources.
Jun 05 10:05:05 kali systemd[1]: Starting Greenbone Vulnerability Manager daemon (gvmd)…
░░ Subject: A start job for unit gvmd.service has begun execution
░░ Defined-By: systemd
░░ Support:
░░
░░ A start job for unit gvmd.service has begun execution.
░░
░░ The job identifier is 9353.
Jun 05 10:05:06 kali systemd[1]: gvmd.service: Can’t open PID file /run/gvmd/gvmd.pid (yet?) after start: Operation not permitted
lines 5529-5579/5579 (END)

2

@George2022 … well. please show errors from logfiles. try apt-get remove --purge gvm and then reinstall?

1 Like
3

Hi Eero,

I have included now a log file in the comment above, I tried the purge before but everything is messed up after, for example, is the purge deletes postgresql then metasploit will not work because it is pointing to postgresql 13 not 14.

thanks,

4

@George2022 how about removing metasploit also and reinstall both packages? that probably fixes the issue.

Eero

1 Like
5

Hi Eero,

thanks, I corrected the error by using these three commands I found:
$ sudo pg_dropcluster 14 main --stop
$ sudo pg_upgradecluster 13 main
$ sudo pg_dropcluster 13 main

thank you!

1 Like