Hello, I recently installed openvas on rhel6 server. I copied the data within /var/lib/openvas for a previous installation on rhel5.
Everything seems fine, but when I launch a scan, it stopped immediately and the following message appears in openvasmd.log: md main:WARNING:2013-04-03 19h06.17 CEST:11112: read_from_server: failed to read from server: A TLS packet with unexpected length was received. Here is the output of openvas-check-setup: which seems ok. Test completeness and readiness of OpenVAS-5 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 3.3.1. OK: OpenVAS Scanner CA Certificate is present as /var/lib/openvas/CA/cacert.pem. OK: NVT collection in /var/lib/openvas/plugins contains 30254 NVTs. OK: Signature checking of NVTs is enabled in OpenVAS Scanner. Step 2: Checking OpenVAS Manager ... OK: OpenVAS Manager is present in version 3.0.5. OK: OpenVAS Manager client certificate is present as /var/lib/openvas/CA/clientcert.pem. 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 56. OK: OpenVAS Manager expects database at revision 56. OK: Database schema is up to date. OK: OpenVAS Manager database contains information about 25563 NVTs. OK: xsltproc found. Step 3: Checking OpenVAS Administrator ... OK: OpenVAS Administrator is present in version 1.2.1. OK: At least one user exists. OK: At least one admin user exists. Step 4: Checking Greenbone Security Assistant (GSA) ... OK: Greenbone Security Assistant is present in version 3.0.3. Step 5: Checking OpenVAS CLI ... OK: OpenVAS CLI version 1.1.5. Step 6: Checking Greenbone Security Desktop (GSD) ... OK: Greenbone Security Desktop is present in Version 1.2.2. 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 all interfaces. OK: OpenVAS Scanner is listening on port 9391, which is the default port. OK: OpenVAS Manager is running and listening on all interfaces. OK: OpenVAS Manager is listening on port 9390, which is the default port. OK: OpenVAS Administrator is running and listening only on the local interface. OK: OpenVAS Administrator is listening on port 9393, which is the default port. OK: Greenbone Security Assistant 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 ... OK: nmap is present in version 5.51. Step 9: 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. WARNING: Could not find alien binary, LSC credential package generation for DEB based targets will not work. SUGGEST: Install alien. OK: nsis found, LSC credential package generation for Microsoft Windows targets is likely to work. It seems like your OpenVAS-5 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. I don't know to fix this, can anyone helps me? Thanks in advance
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
