Hello!
I have it installed on kali linux with the version below, but I can’t get ospd-openvas to work at all
I’ve tried several searches and file permissions, but it seems to be a wrong configuration, can anyone help me with this?
__________________________
└─# neofetch
.............. root@kali
..,;:ccc,. ---------
......''';lxO. OS: Kali GNU/Linux Rolling x86_64
.....''''..........,:ld; Host: Latitude 3440
.';;;:::;,,.x, Kernel: 6.10.11-amd64
..'''. 0Xxoc:,. ... Uptime: 25 mins
.... ,ONkc;,;cokOdc',. Packages: 3546 (dpkg), 33 (flatpak)
. OMo ':ddo. Shell: zsh 5.9
dMc :OO; Resolution: 1920x1080
0M. .:o. DE: GNOME 47.0
;Wd WM: Mutter
;XO, WM Theme: Kali-Dark
,d0Odlc;,.. Theme: Adwaita [GTK2/3]
..',;:cdOOd::,. Icons: Adwaita [GTK2/3]
.:d;.':;. Terminal: gnome-terminal
'd, .' CPU: 12th Gen Intel i5-1235U (12) @ 4.400GHz
;l .. GPU: Intel Alder Lake-UP3 GT2 [Iris Xe Graphics]
.o Memory: 2011MiB / 23724MiB
c
.'
.
__________________________
└─# cat /etc/openvas/openvas.conf
[redis]
unixsocket:/var/run/redis-openvas/redis-server.sock
#unixsocket = var/run/redis-openvas/redis-server.sock
#db_address = var/run/redis-openvas/redis-server.sock
#redis_unix_socket = /var/run/redis-openvas/redis-server.sock
# Use location matching /etc/redis/redis-openvas.conf which is
# used by systemd's redis@openvas.service
#db_address = /var/run/redis-openvas/redis-server.sock
#mqtt_server_uri=redis://127.0.0.1:6379
#mqtt_server_uri=unix:///var/run/redis-openvas/redis-server.sock
#mqtt_server_uri = localhost:1883
#mqtt_server_uri=redis://127.0.0.1:6379
#redis://localhost:6379
__________________________
└─# gvm-check-setup
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.9.0.
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: #db_address = var/run/redis-openvas/redis-server.sock #db_address = /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 92443 NVTs.
OK: The notus directory /var/lib/notus/products contains 469 NVTs.
Checking that the obsolete redis database has been removed
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.
__________________________
└─# redis-cli -s /var/run/redis-openvas/redis-server.sock ping
PONG
└─# redis-cli -s /run/redis-openvas/redis-server.sock ping
PONG
__________________________
└─# cat /etc/gvm/ospd-openvas.conf
[OSPD - openvas]
log_level = DEBUG
socket_mode = 0o770
unix_socket = /run/ospd/ospd.sock
pid_file = /run/ospd/ospd-openvas.pid
log_file = /var/log/gvm/ospd-openvas.log
db_address = /var/run/redis-openvas/redis-server.sock
#redis_url = unix:///var/run/redis-openvas/redis-server.sock
#redis_url = unix:///run/redis-openvas/redis-server.sock
#db_address = /var/run/redis-openvas/redis-server.sock
__________________________
└─# journalctl -xeu ospd-openvas.service
░░ the configured Restart= setting for the unit.
Oct 23 11:25:10 kali systemd[1]: Starting ospd-openvas.service - OSPd Wrapper for the OpenVAS Scanner (ospd-openvas>
░░ Subject: A start job for unit ospd-openvas.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit ospd-openvas.service has begun execution.
░░
░░ The job identifier is 29215.
Oct 23 11:25:35 kali systemd[1]: ospd-openvas.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit ospd-openvas.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Oct 23 11:25:35 kali systemd[1]: ospd-openvas.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit ospd-openvas.service has entered the 'failed' state with result 'exit-code'.
Oct 23 11:25:35 kali systemd[1]: Failed to start ospd-openvas.service - OSPd Wrapper for the OpenVAS Scanner (ospd->
░░ Subject: A start job for unit ospd-openvas.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit ospd-openvas.service has finished with a failure.
░░
░░ The job identifier is 29215 and the job result is failed.
__________________________
└─# tail -f /var/log/gvm/ospd-openvas.log
OSPD[21504] 2024-10-23 14:23:55,197: DEBUG: (ospd_openvas.db) Redis connection lost: Error 2 connecting to unix socket: /run/redis/redis.sock. No such file or directory.. Trying again in 5 seconds.
OSPD[21504] 2024-10-23 14:24:00,199: DEBUG: (ospd_openvas.db) Redis connection lost: Error 2 connecting to unix socket: /run/redis/redis.sock. No such file or directory.. Trying again in 5 seconds.
OSPD[21504] 2024-10-23 14:24:05,200: DEBUG: (ospd_openvas.db) Redis connection lost: Error 2 connecting to unix socket: /run/redis/redis.sock. No such file or directory.. Trying again in 5 seconds.
OSPD[21504] 2024-10-23 14:24:10,201: ERROR: (ospd_openvas.db) Redis Error: Not possible to connect to the kb.
OSPD[21676] 2024-10-23 14:25:10,660: DEBUG: (ospd_openvas.db) Redis connection lost: Error 2 connecting to unix socket: /run/redis/redis.sock. No such file or directory.. Trying again in 5 seconds.
OSPD[21676] 2024-10-23 14:25:15,662: DEBUG: (ospd_openvas.db) Redis connection lost: Error 2 connecting to unix socket: /run/redis/redis.sock. No such file or directory.. Trying again in 5 seconds.
OSPD[21676] 2024-10-23 14:25:20,663: DEBUG: (ospd_openvas.db) Redis connection lost: Error 2 connecting to unix socket: /run/redis/redis.sock. No such file or directory.. Trying again in 5 seconds.
OSPD[21676] 2024-10-23 14:25:25,664: DEBUG: (ospd_openvas.db) Redis connection lost: Error 2 connecting to unix socket: /run/redis/redis.sock. No such file or directory.. Trying again in 5 seconds.
OSPD[21676] 2024-10-23 14:25:30,666: DEBUG: (ospd_openvas.db) Redis connection lost: Error 2 connecting to unix socket: /run/redis/redis.sock. No such file or directory.. Trying again in 5 seconds.
OSPD[21676] 2024-10-23 14:25:35,667: ERROR: (ospd_openvas.db) Redis Error: Not possible to connect to the kb.
OSPD[21793] 2024-10-23 14:26:36,132: DEBUG: (ospd_openvas.db) Redis connection lost: Error 2 connecting to unix socket: /run/redis/redis.sock. No such file or directory.. Trying again in 5 seconds.
OSPD[21793] 2024-10-23 14:26:41,132: DEBUG: (ospd_openvas.db) Redis connection lost: Error 2 connecting to unix socket: /run/redis/redis.sock. No such file or directory.. Trying again in 5 seconds.
OSPD[21793] 2024-10-23 14:26:46,134: DEBUG: (ospd_openvas.db) Redis connection lost: Error 2 connecting to unix socket: /run/redis/redis.sock. No such file or directory.. Trying again in 5 seconds.
OSPD[21793] 2024-10-23 14:26:51,135: DEBUG: (ospd_openvas.db) Redis connection lost: Error 2 connecting to unix socket: /run/redis/redis.sock. No such file or directory.. Trying again in 5 seconds.
OSPD[21793] 2024-10-23 14:26:56,136: DEBUG: (ospd_openvas.db) Redis connection lost: Error 2 connecting to unix socket: /run/redis/redis.sock. No such file or directory.. Trying again in 5 seconds.
OSPD[21793] 2024-10-23 14:27:01,137: ERROR: (ospd_openvas.db) Redis Error: Not possible to connect to the kb.
__________________________
nano /etc/redis/redis-openvas.conf
# on a unix socket when not specified.
#
unixsocket /var/run/redis-openvas/redis-server.sock
unixsocketperm 770
__________________________
└─# systemctl status redis-server@openvas.service
● redis-server@openvas.service - Advanced key-value store (openvas)
Loaded: loaded (/usr/lib/systemd/system/redis-server@.service; disabled; preset: disabled)
Active: active (running) since Wed 2024-10-23 08:46:59 -03; 2h 42min ago
Invocation: 24d28ddba28a45b4a80f27303f788c07
Docs: http://redis.io/documentation,
man:redis-server(1)
Main PID: 6246 (redis-server)
Status: "Ready to accept connections"
Tasks: 5 (limit: 28320)
Memory: 10.4M (peak: 11.1M)
CPU: 26.573s
CGroup: /system.slice/system-redis\x2dserver.slice/redis-server@openvas.service
└─6246 "/usr/bin/redis-server unixsocket:/var/run/redis-openvas/redis-server.sock"
Oct 23 08:46:59 kali redis-server[6246]: Supervised by systemd. Please make sure you set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
Oct 23 08:46:59 kali redis-server[6246]: oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Oct 23 08:46:59 kali redis-server[6246]: Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=6246, just started
Oct 23 08:46:59 kali redis-server[6246]: Configuration loaded
Oct 23 08:46:59 kali redis[6246]: monotonic clock: POSIX clock_gettime
Oct 23 08:46:59 kali redis[6246]: _._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 7.0.15 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 0
| `-._ `._ / _.-' | PID: 6246
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | https://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
Oct 23 08:46:59 kali redis[6246]: Server initialized
Oct 23 08:46:59 kali redis[6246]: WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause>
Oct 23 08:46:59 kali redis[6246]: The server is now ready to accept connections at /var/run/redis-openvas/redis-server.sock
Oct 23 08:46:59 kali systemd[1]: Started redis-server@openvas.service - Advanced key-value store (openvas).
lines 3-40/40 (END)
__________________________
└─# openvas -s
timeout_retry = 3
max_checks = 10
optimize_test = yes
auto_enable_dependencies = yes
checks_read_timeout = 5
time_between_request = 0
allow_simultaneous_ips = yes
non_simult_ports = 139, 445, 3389, Services/irc
drop_privileges = no
log_whole_attack = no
nasl_no_signature_check = yes
cgi_path = /cgi-bin:/scripts
max_hosts = 30
debug_tls = 0
open_sock_max_attempts = 5
config_file = /etc/openvas/openvas.conf
test_alive_wait_timeout = 3
vendor_version =
safe_checks = yes
scanner_plugins_timeout = 36000
include_folders = /var/lib/openvas/plugins
plugins_timeout = 320
log_plugins_name_at_load = no
plugins_folder = /var/lib/openvas/plugins
unscanned_closed = yes
test_empty_vhost = no
report_host_details = yes
expand_vhosts = yes
test_alive_hosts_only = yes
db_address = /run/redis/redis.sock
unscanned_closed_udp = yes
__________________________