I have OPENVAS9 on Kali Linux 2017.3.
I have a VM with 16GB ram memory, 16 processors and disk space over 10GB.
My tasks (mask /24) often do not end due to the error reported in the
attached log file.
Whenever this happens, I execute the commands below to normalize:
redis-cli -s /var/run/redis/redis.sock flushall
Already tried changing parameters of sqlite3 ("pragma
cache_size=10000, pragma synchronous=OFF and vacuum)
and compiling openvas-manager to postgres 10, both unsuccessfully.
I think openvas9 could improve if used postgresql nativerly.
Thank you if anyone could help solve these problems.
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
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.7.
OK: scanner (kb_location setting) is configured properly using the
redis-server socket: /var/run/redis/redis.sock
OK: redis-server is running and listening on socket:
OK: redis-server configuration is OK and redis-server is running.
OK: NVT collection in /var/lib/openvas/plugins contains 56000 NVTs.
WARNING: Signature checking of NVTs is not enabled in OpenVAS Scanner.
SUGGEST: Enable signature checking (see
OK: The NVT cache in /var/cache/openvas contains 58078 files for 56000
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
OK: OpenVAS Manager database is at revision 184.
OK: OpenVAS Manager expects database at revision 184.
OK: Database schema is up to date.
OK: OpenVAS Manager database contains information about 55999 NVTs.
OK: At least one user exists.
OK: OpenVAS SCAP database found in /var/lib/openvas/scap-data/scap.db.
OK: OpenVAS CERT database found in /var/lib/openvas/cert-data/cert.db.
OK: xsltproc found.
Step 3: Checking user configuration ...
WARNING: Your password policy is empty.
SUGGEST: Edit the /etc/openvas/pwpolicy.conf file to set a password
Step 4: Checking Greenbone Security Assistant (GSA) ...
OK: Greenbone Security Assistant is present in version 7.0.2.
OK: Your OpenVAS certificate infrastructure passed validation.
Step 5: Checking OpenVAS CLI ...
OK: OpenVAS CLI version 1.4.5.
Step 6: Checking Greenbone Security Desktop (GSD) ...
SKIP: Skipping check for Greenbone Security Desktop.
Step 7: Checking if OpenVAS services are up and running ...
OK: netstat found, extended checks of the OpenVAS services enabled.
OK: OpenVAS Scanner is running and listening on a Unix domain socket.
ERROR: OpenVAS Manager is NOT running!
FIX: Start OpenVAS Manager (openvasmd).
OK: Greenbone Security Assistant is listening on port 80, which is the
ERROR: Your OpenVAS-9 installation is not yet complete!
Please follow the instructions marked with FIX above and run this
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
firstname.lastname@example.org:~# tail -f /var/log/openvas/openvasmd.log
md otp:MESSAGE:2018-02-14 17h31.03 utc:15528: Waiting for scanner to load
NVTs: 25850 / 56000.
md otp:MESSAGE:2018-02-14 17h31.14 utc:18081: Waiting for scanner to load
NVTs: 31550 / 56000.
md otp:MESSAGE:2018-02-14 17h31.26 utc:20712: Waiting for scanner to load
NVTs: 38200 / 56000.
md otp:MESSAGE:2018-02-14 17h31.37 utc:23517: Waiting for scanner to load
NVTs: 45350 / 56000.
md otp:MESSAGE:2018-02-14 17h31.48 utc:26410: Waiting for scanner to load
NVTs: 51400 / 56000.
md manage:WARNING:2018-02-14 18h36.26 utc:706: sql_exec_internal: sqlite3_step
failed: cannot start a transaction within a transaction
md manage:WARNING:2018-02-14 18h36.26 utc:706: sqlv: sql_exec_internal failed
md manage:WARNING:2018-02-14 18h36.26 utc:706: manage_schedule:
md main:MESSAGE:2018-02-14 20h07.41 utc:21753: OpenVAS Manager version
7.0.2 (DB revision 184)
md manage: INFO:2018-02-14 20h07.41 utc:21753: Getting users.
Openvas-discuss mailing list