Hello Everyone, I use OpenVAS 9 in Kali Linux 2018.3. Does anyone know how to solve the problem above ? For more details, see attached file.
tks Maso, J.
root@kali:~# tail -f /var/log/openvas/openvasmd.log event task:MESSAGE:2018-09-13 17h43.41 -03:17435: Task a5adaa3d-ddeb-473c-a660-2fc845d5dc79 for servicos (1a166366-a29d-40d1-8e72-1f6acd0d135b) has been created by slave event task:MESSAGE:2018-09-13 17h43.42 -03:17435: Status of task a5adaa3d-ddeb-473c-a660-2fc845d5dc79 for servicos (1a166366-a29d-40d1- 8e72-1f6acd0d135b) has changed to Requested event task:MESSAGE:2018-09-13 17h43.42 -03:17435: Task a5adaa3d-ddeb-473c-a660-2fc845d5dc79 for servicos (1a166366-a29d-40d1-8e72-1f6acd0d135b) has been requested to start by slave event task:MESSAGE:2018-09-13 17h43.55 -03:17438: Status of task a5adaa3d-ddeb-473c-a660-2fc845d5dc79 for servicos (1a166366-a29d-40d1- 8e72-1f6acd0d135b) has changed to Running md main:WARNING:2018-09-13 17h44.04 -03:17438: openvas_scanner_read: Failed to read from scanner: Connection reset by peer event task:MESSAGE:2018-09-13 17h44.04 -03:17438: Status of task a5adaa3d-ddeb-473c-a660-2fc845d5dc79 for servicos (1a166366-a29d-40d1- 8e72-1f6acd0d135b) has changed to Stopped ^C root@kali:~# openvas-check-setup openvas-check-setup 2.3.7 Test completeness and readiness of OpenVAS-9 (add '--v6' or '--v7' or '--v8' if you want to check for another OpenVAS version) Please report us any non-detected problems and help us to improve this check routine: http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss 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.3. OK: redis-server is present in version v=4.0.11. OK: scanner (kb_location setting) is configured properly using the redis-server socket: /var/run/redis-openvas/redis-server.sock OK: redis-server is running and listening on socket: /var/run/redis-openvas/redis-server.sock. OK: redis-server configuration is OK and redis-server is running. OK: NVT collection in /var/lib/openvas/plugins contains 47185 NVTs. WARNING: Signature checking of NVTs is not enabled in OpenVAS Scanner. SUGGEST: Enable signature checking (see http://www.openvas.org/trusted-nvts.html). OK: The NVT cache in /var/cache/openvas contains 61315 files for 47185 NVTs. Step 2: Checking OpenVAS Manager ... OK: OpenVAS Manager is present in version 7.0.3. 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. OK: OpenVAS Manager database contains information about 46496 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 policy. Step 4: Checking Greenbone Security Assistant (GSA) ... OK: Greenbone Security Assistant is present in version 7.0.3. 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. OK: OpenVAS Manager is running and listening on all interfaces. OK: Greenbone Security Assistant is listening on port 443, which is the default port. Step 8: Checking nmap installation ... WARNING: Your version of nmap is not fully supported: 7.70 SUGGEST: You should install nmap 5.51 if you plan to use the nmap NSE NVTs. Step 10: Checking presence of optional tools ... OK: pdflatex found. OK: PDF generation successful. The PDF report format is likely to work. OK: ssh-keygen found, LSC credential generation for GNU/Linux targets is likely to work. OK: rpm found, LSC credential package generation for RPM based targets is likely to work. OK: alien found, LSC credential package generation for DEB based targets is likely to work. OK: nsis found, LSC credential package generation for Microsoft Windows targets is likely to work. It seems like your OpenVAS-9 installation is OK. If you think it is not OK, please report your observation and help us to improve this check routine: http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem. root@kali:~# netstat -tulnep Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:9390 0.0.0.0:* LISTEN 0 20140 959/openvasmd tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 12146 971/gsad tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 21009 985/sshd tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 0 18990 953/gsad tcp6 0 0 :::22 :::* LISTEN 0 21007 985/sshd root@kali:~# uname -v #1 SMP Debian 4.17.17-1kali1 (2018-08-21)
_______________________________________________ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
