If I run openvassd --unix-socket=/tmp/redis.sock &
I don’t have errors but web access is not work…
Hello I am in trouble with openvas under Armbian with Orange Pi Zero.
I used this guide to intall it::
root@OpiZero:/# netstat -vnepl |grep redis
netstat: no support for AF INET (sctp)' on this system. netstat: no support for AF INET (sctp)’ on this system.
netstat: no support for AF IPX' on this system. netstat: no support for AF AX25’ on this system.
netstat: no support for AF X25' on this system. netstat: no support for AF NETROM’ on this system.
netstat: no support for `AF ROSE’ on this system.
tcp 0 0 127.0.0.1:64010 0.0.0.0:* LISTEN 109 34979 3015/redis-server 1
tcp6 0 0 ::1:64010 :::* LISTEN 109 34980 3015/redis-server 1
unix 2 [ ACC ] STREAM LISTENING 34981 3015/redis-server 1 /tmp/redis.sock
root@OpiZero:/#
I changed socket settings in /etc/redis/redis.conf
Port to 64010
and socket settings to:
unixsocket /tmp/redis.sock
unixsocketperm 755
But doesn’t help.
Can you help me to install it in Armbian ?
Linux OpiZero 5.4.20-sunxi #20.02.1 SMP Mon Feb 17 02:09:41 CET 2020 armv7l armv7l armv7l GNU/Linux
root@OpiZero:/# openvas-setup
OK: Directory for keys (/var/lib/openvas/private/CA) exists.
OK: Directory for certificates (/var/lib/openvas/CA) exists.
OK: CA key found in /var/lib/openvas/private/CA/cakey.pem
OK: CA certificate found in /var/lib/openvas/CA/cacert.pem
OK: CA certificate verified.
OK: Certificate /var/lib/openvas/CA/servercert.pem verified.
OK: Certificate /var/lib/openvas/CA/clientcert.pem verified.
OK: Your OpenVAS certificate infrastructure passed validation.
Greenbone community feed server -
This service is hosted by Greenbone Networks -
All transactions are logged.
If you have any questions, please use the Greenbone community portal.
See for details.
By using this service you agree to our terms and conditions.
Only one sync per time, otherwise the source ip will be temporarily blocked.
receiving incremental file list
plugin_feed_info.inc
985 100% 961.91kB/s 0:00:00 (xfr#1, to-chk=0/1)
sent 43 bytes received 1,096 bytes 2,278.00 bytes/sec
total size is 985 speedup is 0.86
Greenbone community feed server -
This service is hosted by Greenbone Networks -
All transactions are logged.
If you have any questions, please use the Greenbone community portal.
See for details.
By using this service you agree to our terms and conditions.
Only one sync per time, otherwise the source ip will be temporarily blocked.
receiving incremental file list
timestamp
13 100% 12.70kB/s 0:00:00 (xfr#1, to-chk=0/1)
sent 43 bytes received 114 bytes 314.00 bytes/sec
total size is 13 speedup is 0.08
Greenbone community feed server -
This service is hosted by Greenbone Networks -
All transactions are logged.
If you have any questions, please use the Greenbone community portal.
See for details.
By using this service you agree to our terms and conditions.
Only one sync per time, otherwise the source ip will be temporarily blocked.
receiving incremental file list
timestamp
13 100% 12.70kB/s 0:00:00 (xfr#1, to-chk=0/1)
sent 43 bytes received 114 bytes 44.86 bytes/sec
total size is 13 speedup is 0.08
(openvassd:3150): lib kb_redis-CRITICAL **: 18:41:20.329: get_redis_ctx: redis connection error: Connection refused
(openvassd:3150): lib kb_redis-CRITICAL **: 18:41:20.329: redis_new: cannot access redis at ‘/tmp/redis.sock’
(openvassd:3150): lib kb_redis-CRITICAL **: 18:41:20.329: get_redis_ctx: redis connection error: Connection refused
openvassd: no process found
root@OpiZero:/etc/openvas# openvassd
(openvassd:2163): lib kb_redis-CRITICAL **: 17:26:17.523: get_redis_ctx: redis connection error: Connection refused
(openvassd:2163): lib kb_redis-CRITICAL **: 17:26:17.524: redis_new: cannot access redis at ‘/tmp/redis.sock’
(openvassd:2163): lib kb_redis-CRITICAL **: 17:26:17.524: get_redis_ctx: redis connection error: Connection refused
root@OpiZero:/# journalctl -xe
– The start-up result is RESULT.
Mar 08 20:00:38 OpiZero nm-dispatcher[2572]: req:1 ‘dhcp4-change’ [wlan0]: new request (2 script
Mar 08 20:00:38 OpiZero nm-dispatcher[2572]: req:1 ‘dhcp4-change’ [wlan0]: start running ordered
Mar 08 20:00:44 OpiZero kernel: xradio WRN: BH: missed 50 consecutive interrupts!
Mar 08 20:00:46 OpiZero kernel: xradio WRN: BH: missed 51 consecutive interrupts!
Mar 08 20:01:26 OpiZero kernel: xradio WRN: BH: missed 52 consecutive interrupts!
Mar 08 20:01:35 OpiZero kernel: xradio WRN: BH: missed 53 consecutive interrupts!
Mar 08 20:02:46 OpiZero wpa_supplicant[804]: wlan0: WPA: Group rekeying completed with c6:ad:34:
Mar 08 20:02:53 OpiZero systemd[1]: Starting Open Vulnerability Assessment System Scanner Daemon
– Subject: Unit openvas-scanner.service has begun start-up
– Defined-By: systemd
– Support:
– Unit openvas-scanner.service has begun starting up.
Mar 08 20:04:23 OpiZero systemd[1]: openvas-scanner.service: Start operation timed out. Terminat
Mar 08 20:04:23 OpiZero systemd[1]: openvas-scanner.service: Failed with result ‘timeout’.
Mar 08 20:04:23 OpiZero systemd[1]: Failed to start Open Vulnerability Assessment System Scanner
– Subject: Unit openvas-scanner.service has failed
– Defined-By: systemd
– Support:
– Unit openvas-scanner.service has failed.
– The result is RESULT.
root@OpiZero:/# openvas-check-setup --v9
openvas-check-setup 2.3.7
Test completeness and readiness of OpenVAS-9
Please report us any non-detected problems and
help us to improve this check routine:
Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem.
Use the parameter --server to skip checks for client tools
like GSD and OpenVAS-CLI.
Step 1: Checking OpenVAS Scanner …
OK: OpenVAS Scanner is present in version 5.1.1.
OK: redis-server is present in version v=4.0.9.
OK: scanner (kb_location setting) is configured properly using the redis-server socket: /tmp/redis.sock
OK: redis-server is running and listening on socket: /tmp/redis.sock.
OK: redis-server configuration is OK and redis-server is running.
OK: NVT collection in /var/lib/openvas/plugins contains 58086 NVTs.
WARNING: Signature checking of NVTs is not enabled in OpenVAS Scanner.
SUGGEST: Enable signature checking (see ).
WARNING: The initial NVT cache has not yet been generated.
SUGGEST: Start OpenVAS Scanner for the first time to generate the cache.
Step 2: Checking OpenVAS Manager …
OK: OpenVAS Manager is present in version 7.0.2.
OK: OpenVAS Manager database found in /var/lib/openvas/mgr/tasks.db.
OK: Access rights for the OpenVAS Manager database are correct.
OK: sqlite3 found, extended checks of the OpenVAS Manager installation enabled.
OK: OpenVAS Manager database is at revision 184.
OK: OpenVAS Manager expects database at revision 184.
OK: Database schema is up to date.
ERROR: The number of NVTs in the OpenVAS Manager database is too low.
FIX: Make sure OpenVAS Scanner is running with an up-to-date NVT collection and run ‘openvasmd --rebuild’.
WARNING: OpenVAS Scanner is NOT running!
SUGGEST: Start OpenVAS Scanner (openvassd).
ERROR: Your OpenVAS-9 installation is not yet complete!
Please follow the instructions marked with FIX above and run this
script again.
If you think this result is wrong, please report your observation
and help us to improve this check routine:
Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem.
GNU nano 2.9.3 /tmp/openvas-check-setup.log
openvas-check-setup 2.3.7
Mode: desktop
Date: Sun, 08 Mar 2020 20:07:47 +0200
Checking for old OpenVAS Scanner <= 2.0 …
/usr/bin/openvas-check-setup: 172: /usr/bin/openvas-check-setup: openvasd: not found
Checking presence of OpenVAS Scanner …
OpenVAS Scanner 5.1.1
Most new code since 2005: © 2016 Greenbone Networks GmbH
Nessus origin: © 2004 Renaud Deraison <>
License GPLv2: GNU GPL version 2
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Checking OpenVAS Scanner version …
ERROR: OpenVAS Scanner too old or too new: 5.1.1
FIX: Please install OpenVAS Scanner 5.0.
HINT: Please see the --v6/7/8/9 command line options to check other major versions.
openvas-check-setup 2.3.7
openvas-check-setup 2.3.7
Test completeness and readiness of OpenVAS-8
(add ‘–v6’ or ‘–v7’ or ‘–v9’
if you want to check for another OpenVAS version)
Please report us any non-detected problems and
help us to improve this check routine:
Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem.
Use the parameter --server to skip checks for client tools
like GSD and OpenVAS-CLI.
Step 1: Checking OpenVAS Scanner …
ERROR: OpenVAS Scanner too old or too new: 5.1.1
FIX: Please install OpenVAS Scanner 5.0.
HINT: Please see the --v6/7/8/9 command line options to check other major versions.
ERROR: Your OpenVAS-8 installation is not yet complete!
Please follow the instructions marked with FIX above and run this
script again.
If you think this result is wrong, please report your observation
and help us to improve this check routine:
Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem.
root@OpiZero:/# openvas-check-setup --v6
openvas-check-setup 2.3.7
Test completeness and readiness of OpenVAS-6
Please report us any non-detected problems and
help us to improve this check routine:
Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem.
Use the parameter --server to skip checks for client tools
like GSD and OpenVAS-CLI.
Step 1: Checking OpenVAS Scanner …
ERROR: OpenVAS Scanner too old or too new: 5.1.1
FIX: Please install OpenVAS Scanner 3.4.
HINT: Please see the --v6/7/8/9 command line options to check other major versions.
ERROR: Your OpenVAS-6 installation is not yet complete!
Please follow the instructions marked with FIX above and run this
script again.
If you think this result is wrong, please report your observation
and help us to improve this check routine:
Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem.
root@OpiZero:/# openvas-check-setup --v7
openvas-check-setup 2.3.7
Test completeness and readiness of OpenVAS-7
Please report us any non-detected problems and
help us to improve this check routine:
Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem.
Use the parameter --server to skip checks for client tools
like GSD and OpenVAS-CLI.
Step 1: Checking OpenVAS Scanner …
ERROR: OpenVAS Scanner too old or too new: 5.1.1
FIX: Please install OpenVAS Scanner 4.0.
HINT: Please see the --v6/7/8/9 command line options to check other major versions.
ERROR: Your OpenVAS-7 installation is not yet complete!
Please follow the instructions marked with FIX above and run this
script again.
If you think this result is wrong, please report your observation
and help us to improve this check routine:
Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem.
root@OpiZero:/# openvas-check-setup --v8
openvas-check-setup 2.3.7
Test completeness and readiness of OpenVAS-8
(add ‘–v6’ or ‘–v7’ or ‘–v9’
if you want to check for another OpenVAS version)
Please report us any non-detected problems and
help us to improve this check routine:
Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem.
Use the parameter --server to skip checks for client tools
like GSD and OpenVAS-CLI.
Step 1: Checking OpenVAS Scanner …
ERROR: OpenVAS Scanner too old or too new: 5.1.1
FIX: Please install OpenVAS Scanner 5.0.
HINT: Please see the --v6/7/8/9 command line options to check other major versions.
ERROR: Your OpenVAS-8 installation is not yet complete!
Please follow the instructions marked with FIX above and run this
script again.
If you think this result is wrong, please report your observation
and help us to improve this check routine:
Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem.
root@OpiZero:/# openvas-check-setup --v9
openvas-check-setup 2.3.7
Test completeness and readiness of OpenVAS-9
Please report us any non-detected problems and
help us to improve this check routine:
Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem.
Use the parameter --server to skip checks for client tools
like GSD and OpenVAS-CLI.
Step 1: Checking OpenVAS Scanner …
OK: OpenVAS Scanner is present in version 5.1.1.
OK: redis-server is present in version v=4.0.9.
OK: scanner (kb_location setting) is configured properly using the redis-server socket: /tmp/redis.sock
OK: redis-server is running and listening on socket: /tmp/redis.sock.
OK: redis-server configuration is OK and redis-server is running.
OK: NVT collection in /var/lib/openvas/plugins contains 58086 NVTs.
WARNING: Signature checking of NVTs is not enabled in OpenVAS Scanner.
SUGGEST: Enable signature checking (see ).
WARNING: The initial NVT cache has not yet been generated.
SUGGEST: Start OpenVAS Scanner for the first time to generate the cache.
Step 2: Checking OpenVAS Manager …
OK: OpenVAS Manager is present in version 7.0.2.
OK: OpenVAS Manager database found in /var/lib/openvas/mgr/tasks.db.
OK: Access rights for the OpenVAS Manager database are correct.
OK: sqlite3 found, extended checks of the OpenVAS Manager installation enabled.
OK: OpenVAS Manager database is at revision 184.
OK: OpenVAS Manager expects database at revision 184.
OK: Database schema is up to date.
ERROR: The number of NVTs in the OpenVAS Manager database is too low.
FIX: Make sure OpenVAS Scanner is running with an up-to-date NVT collection and run ‘openvasmd --rebuild’.
WARNING: OpenVAS Scanner is NOT running!
SUGGEST: Start OpenVAS Scanner (openvassd).
ERROR: Your OpenVAS-9 installation is not yet complete!
Please follow the instructions marked with FIX above and run this
script again.
If you think this result is wrong, please report your observation
and help us to improve this check routine:
Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem.