Hi all, I tryied many times to install gvm but I have always the same error
I have followed the installation guide , many youtube video but nothing,
this is the error:
gvm-check-setup 23.11.0
Test completeness and readiness of GVM-23.11.0
Step 1: Checking OpenVAS (Scanner)…
OK: OpenVAS Scanner is present in version 23.13.1.
OK: Notus Scanner is present in version 22.6.4.
OK: Server CA Certificate is present as /var/lib/gvm/CA/servercert.pem.
Checking permissions of /var/lib/openvas/gnupg/*
OK: _gvm owns all files in /var/lib/openvas/gnupg
OK: redis-server is present.
OK: scanner (db_address setting) is configured properly using the redis-server socket: /var/run/redis-openvas/redis-server.sock
OK: the mqtt_server_uri is defined in /etc/openvas/openvas.conf
OK: _gvm owns all files in /var/lib/openvas/plugins
OK: NVT collection in /var/lib/openvas/plugins contains 93040 NVTs.
OK: The notus directory /var/lib/notus/products contains 472 NVTs.
Checking that the obsolete redis database has been removed
Could not connect to Redis at /var/run/redis-openvas/redis-server.sock: No such file or directory
OK: No old Redis DB
Starting ospd-openvas service Job for ospd-openvas.service failed because the control process exited with error code. See “systemctl status ospd-openvas.service” and “journalctl -xeu ospd-openvas.service” for details.
Waiting for ospd-openvas service
ERROR: ospd-openvas service did not start.
Please check journalctl -xe
ERROR: Your GVM-23.11.0 installation is not yet complete!
Please follow the instructions marked with FIX above and run this
script again.
You’re doing great so far. I suggest you first read up on those commands to understand what they do, how to use them, etc. Then use them to view the logs and see if they explain what the issue is. Sometimes it’s a simple thing that can be easily fixed.
In general, if the only error you see or the only information you have is easy to read and understand, but does not seem to provide any real information as to what the issue is, posting it here isn’t going to help us understand the issue any better so we can help you fix it. We need real information.
I understand you are new so one of the first things I recommend you familiarize yourself with is logging functionality and how to access logs to gather information. This is an important step in troubleshooting and it will help you solve a lot of your own issues, but more importantly it will allow you to gather useful information you can pass along to people when you’re asking for help.
ournalctl -xeu ospd-openvas.service
gen 03 14:11:03 Host-019 ospd-openvas[134360]: File “/usr/lib/python3/dist-packages/ospd_openvas/db.py”, line 431, in init
gen 03 14:11:03 Host-019 ospd-openvas[134360]: self.ctx = OpenvasDB.create_context(kbindex)
gen 03 14:11:03 Host-019 ospd-openvas[134360]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
gen 03 14:11:03 Host-019 ospd-openvas[134360]: File “/usr/lib/python3/dist-packages/ospd_openvas/db.py”, line 102, in create_context
gen 03 14:11:03 Host-019 ospd-openvas[134360]: ctx = redis.Redis.from_url(
gen 03 14:11:03 Host-019 ospd-openvas[134360]: ^^^^^^^^^^^^^^^^^^^^^
gen 03 14:11:03 Host-019 ospd-openvas[134360]: File “/usr/lib/python3/dist-packages/redis/client.py”, line 897, in from_url
gen 03 14:11:03 Host-019 ospd-openvas[134360]: connection_pool = ConnectionPool.from_url(url, **kwargs)
gen 03 14:11:03 Host-019 ospd-openvas[134360]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
gen 03 14:11:03 Host-019 ospd-openvas[134360]: File “/usr/lib/python3/dist-packages/redis/connection.py”, line 1275, in from_url
gen 03 14:11:03 Host-019 ospd-openvas[134360]: url_options = parse_url(url)
gen 03 14:11:03 Host-019 ospd-openvas[134360]: ^^^^^^^^^^^^^^
gen 03 14:11:03 Host-019 ospd-openvas[134360]: File “/usr/lib/python3/dist-packages/redis/connection.py”, line 1212, in parse_url
gen 03 14:11:03 Host-019 ospd-openvas[134360]: raise ValueError(
gen 03 14:11:03 Host-019 ospd-openvas[134360]: ValueError: Redis URL must specify one of the following schemes (redis://, rediss://, unix://)
gen 03 14:11:03 Host-019 systemd[1]: ospd-openvas.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Uscito processo unità
░░ Defined-By: systemd
░░
░░ Un processo ExecStart appartenente all’unità ospd-openvas.service è uscito.
░░
░░ Il codice di uscita del processo è ‘exited’ ed è uscito con 1.
gen 03 14:11:03 Host-019 systemd[1]: ospd-openvas.service: Failed with result ‘exit-code’.
░░ Subject: Unit fallita
░░ Defined-By: systemd
░░
░░ Unità ospd-openvas.service entrata nello stato ‘failed’ (fallito) con risultato ‘exit-code’.
gen 03 14:11:03 Host-019 systemd[1]: Failed to start ospd-openvas.service - OSPd Wrapper for the OpenVAS Scanner (ospd-openvas).
░░ Subject: L’unità ospd-openvas.service è fallita
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ L’unità ospd-openvas.service è fallita.
░░
░░ Il risultato è failed.
I googled around and found a thread where it appears the issue might be permissions set by running openvas -s for the first time as root, which creates the openvas log file as root, setting root as its owner. You’d need to change the owner to the _gvm user.
hi @dave
you are right , in meantime I searched by my self also and I found a command chmod 666 … etc to change permissions on openvas.log
seems solved now.
Glad it helped. Be aware that setting permissions to broadly is generally not advised. The solution of changing the owner of the file is considered better practice. It might not matter too much if this is just a local system to practice on, But something to consider