Failed to verify scanner: Service unavailable

[yeet]

GVM versions

gsad: Greenbone Security Assistant 9.0.1~git-a3efc22f0-gsa-9.0 (this shows up an error: Oops, secure memory pool already initialized)
gvmd: Greenbone Vulnerability Manager 9.0.1~git-40b9427e7-gvmd-9.0
openvas-scanner: OpenVAS 7.0.1
gvm-libs: gvm-libs 11.0.1

Environment

Operating system: Ubuntu 20.04.1 LTS (focal)
Kernel: Linux ubuntuserver 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Installation method / source: Install script from Github: GitHub - yu210148/gvm_install: A script to install GVM 20 or 21 on Ubuntu 20.04 or Debian 10.

Hello guys,

I have an issue with my installation. Every time I boot up the system (wait some minutes) and verify the scanner. It shows up with the error: Service unavailable
As far as I can see is everything normal, but apparently not. Anybody knows what could be wrong?
When I run the install script, it’s working again (untill reboot). The first days/weeks I’ve used the installation with this script, I didn’t have this problem.

Service status:

marvin@ubuntuserver:~$ sudo systemctl status openvas
● openvas.service - Control the OpenVAS service
Loaded: loaded (/etc/systemd/system/openvas.service; enabled; vendor preset: enabled)
Active: active (exited) since Tue 2020-11-24 10:14:29 UTC; 10min ago
Process: 1091 ExecStartPre=/usr/bin/rm /opt/gvm/var/run/ospd-openvas.pid /opt/gvm/var/run/ospd.sock /opt/gvm/var/run/gvmd.sock (code=exited, status=1/FAILURE)
Process: 1092 ExecStart=/usr/bin/python3 /opt/gvm/bin/ospd-openvas --pid-file /opt/gvm/var/run/ospd-openvas.pid --log-file /opt/gvm/var/log/gvm/ospd-openvas.log --lock-file-dir /opt/gvm/var/run -u /opt/gvm/var/run/ospd.sock (code=ex>
Main PID: 1092 (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 9417)
Memory: 26.7M
CGroup: /system.slice/openvas.service
└─1105 /usr/bin/python3 /opt/gvm/bin/ospd-openvas --pid-file /opt/gvm/var/run/ospd-openvas.pid --log-file /opt/gvm/var/log/gvm/ospd-openvas.log --lock-file-dir /opt/gvm/var/run -u /opt/gvm/var/run/ospd.sock

Nov 24 10:14:29 ubuntuserver systemd[1]: Starting Control the OpenVAS service…
Nov 24 10:14:29 ubuntuserver rm[1091]: /usr/bin/rm: cannot remove ‘/opt/gvm/var/run/ospd-openvas.pid’: No such file or directory
Nov 24 10:14:29 ubuntuserver rm[1091]: /usr/bin/rm: cannot remove ‘/opt/gvm/var/run/ospd.sock’: No such file or directory
Nov 24 10:14:29 ubuntuserver systemd[1]: Started Control the OpenVAS service.

marvin@ubuntuserver:~$ sudo systemctl status gvm
● gvm.service - Control the OpenVAS GVM service
Loaded: loaded (/etc/systemd/system/gvm.service; enabled; vendor preset: enabled)
Active: active (exited) since Tue 2020-11-24 10:14:29 UTC; 11min ago
TriggeredBy: ● gvm.path
Process: 1094 ExecStart=/opt/gvm/sbin/gvmd --osp-vt-update=/opt/gvm/var/run/ospd.sock (code=exited, status=0/SUCCESS)
Main PID: 1094 (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 9417)
Memory: 151.7M
CGroup: /system.slice/gvm.service
└─1102 gvmd: Waiting for incoming connections

Nov 24 10:14:29 ubuntuserver systemd[1]: Started Control the OpenVAS GVM service.
marvin@ubuntuserver:~$ sudo systemctl status redis
● redis-server.service - Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2020-11-24 10:14:27 UTC; 11min ago
Docs: https://redis.io/docs/,
man:redis-server(1)
Process: 921 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=0/SUCCESS)
Main PID: 995 (redis-server)
Tasks: 4 (limit: 9417)
Memory: 3.4M
CGroup: /system.slice/redis-server.service
└─995 /usr/bin/redis-server 127.0.0.1:6379

Nov 24 10:14:27 ubuntuserver systemd[1]: Starting Advanced key-value store…
Nov 24 10:14:27 ubuntuserver systemd[1]: Started Advanced key-value store.
marvin@ubuntuserver:~$ sudo systemctl status postgresql
● postgresql.service - PostgreSQL RDBMS
Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)
Active: active (exited) since Tue 2020-11-24 10:14:29 UTC; 11min ago
Process: 1090 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 1090 (code=exited, status=0/SUCCESS)

Nov 24 10:14:29 ubuntuserver systemd[1]: Starting PostgreSQL RDBMS…
Nov 24 10:14:29 ubuntuserver systemd[1]: Finished PostgreSQL RDBMS.
marvin@ubuntuserver:~$

EDIT:
It works some reboots. And after that not anymore. Usually it works the whole day. When I boot next day, it doesn’t work anymore.

[cfi]

If that issue starts to happen after a reboot it’s very likely that the service files provided by that 3rdparty install script has some issue. I would raise an issue about that on https://github.com/yu210148/gvm_install/issues

[yeet]

I didn’t see the issue for weeks now. Untill tomorrow. It is back again. So it is not after every reboot.
I am thinking more about network changes (and vmware).
Like. Now I am working in a different place than usual in my house; on WiFi. Usually I am working on LAN.

[yu210148]

Hi there,

cfi is right, there were some issues with the python path and version in the service files it created. I’ve since updated the (admittedly 3rd party) script so that folks shouldn’t run into this anymore. There are a couple of options at this point for you: 1). use the supported community edition that Greenbone releases, 2). re-run the updated gvm_install script on a fresh Ubuntu 20.04 machine / VM–I’ve just added support for GVM ver. 20.xx so this has the added bonus that you can upgrade to that version from GVM 11. Or 3)., if you’d like to try to salvage the existing installation take a look in /etc/systemd/system and modify the openvas, gvm, and gsa service files. Check that the python paths in them match your installed python3 version. The python3 version can be checked with “python3 --version”.

There might be some other nonsense going on but that’s definitely an issue that I’ve run into on occasion.

kev.

[cfi]

Thanks a lot for providing this info / jumping in here.

If there are any questions / issues left you’re welcome to discuss them here at the community portal