Hi List My scans seem to begin then fail with "internal error", using the Greenbone gsa. Scanning via a slave, the scan seems to begin fine, however shortly after running it dies with the following messages:
-- [Mon Dec 22 13:26:32 2014][14626] SIGSEGV occured ! [Mon Dec 22 13:26:32 2014][14626] closing logfile [Mon Dec 22 13:26:32 2014][13469] Process 14626 seems to have died too early -- I have openvas installed via yum on CentOS 6.5: -- openvas-libraries-7.0.6-15.el6.art.x86_64 openvas-cli-1.3.1-6.el6.art.x86_64 openvas-manager-5.0.7-25.el6.art.x86_64 openvas-scanner-4.0.5-17.el6.art.x86_64 openvas-1.0-13.el6.art.noarch --- I'd appreciate it if someone could shed some light on this issue! Some log context from the slave: --- [Mon Dec 22 13:25:56 2014][13446] openvassd 4.0.3 started ==> openvasmd.log <== lib serv: DEBUG:2014-12-22 13h26.10 utc:13452: Shook hands with peer. lib serv: DEBUG:2014-12-22 13h26.10 utc:13452: Connected to server on socket 10. lib serv: DEBUG:2014-12-22 13h26.10 utc:13452: Shook hands with peer. base gpgme:MESSAGE:2014-12-22 13h26.10 UTC:13452: Setting GnuPG homedir to '/var/lib/openvas/gnupg' base gpgme:MESSAGE:2014-12-22 13h26.10 UTC:13452: Using OpenPGP engine version '2.0.14' event lsc_credential:MESSAGE:2014-12-22 13h26.10 UTC:13452: LSC Credential bf651651-d974-4bb7-855a-a695ae72d71f has been created by admin event target:MESSAGE:2014-12-22 13h26.10 UTC:13452: Target 881fbfbc-3e83-4a59-b114-27e214353fe9 has been created by admin event config:MESSAGE:2014-12-22 13h26.11 UTC:13452: Scan config 8056a4f1-e95e-410a-9998-4bf62215bd9f has been created by admin event task:MESSAGE:2014-12-22 13h26.11 UTC:13452: Status of task (6d895a7f-ace7-4f39-a53e-098956dcca59) has changed to New event task:MESSAGE:2014-12-22 13h26.11 UTC:13452: Task 6d895a7f-ace7-4f39-a53e-098956dcca59 has been created by admin event task:MESSAGE:2014-12-22 13h26.11 UTC:13452: Status of task 50172e6b-ba89-4362-a222-3a10fa526cc9 (6d895a7f-ace7-4f39-a53e-098956dcca59) has changed to Requested event task:MESSAGE:2014-12-22 13h26.12 UTC:13452: Task 6d895a7f-ace7-4f39-a53e-098956dcca59 has been requested to start by admin event task:MESSAGE:2014-12-22 13h26.14 UTC:13466: Status of task 50172e6b-ba89-4362-a222-3a10fa526cc9 (6d895a7f-ace7-4f39-a53e-098956dcca59) has changed to Running ==> openvassd.log <== [Mon Dec 22 13:26:19 2014][13453] Starts a new scan. Target(s) : 172.16.104.145, with max_hosts = 20 and max_checks = 4 [Mon Dec 22 13:26:19 2014][13453] Testing 172.16.104.145 (::ffff:172.16.104.145) [13469] [Mon Dec 22 13:26:32 2014][14626] SIGSEGV occured ! [Mon Dec 22 13:26:32 2014][14626] closing logfile [Mon Dec 22 13:26:32 2014][13469] Process 14626 seems to have died too early ==> openvasmd.log <== md main: DEBUG:2014-12-22 13h26.37 UTC:13452: report_severity: max(severity)=0.0 md main: DEBUG:2014-12-22 13h26.37 UTC:13452: command: /bin/sh /usr/share/openvas/openvasmd/global_report_formats/a994b278-1f62-11e1-96ac-406186ea4fc5/generate /tmp/openvasmd_HwR1GE/report.xml > /tmp/openvasmd_HwR1GE/report.out 2> /dev/null md main: DEBUG:2014-12-22 13h27.03 UTC:13452: report_severity: max(severity)=0.0 md main: DEBUG:2014-12-22 13h27.03 UTC:13452: command: /bin/sh /usr/share/openvas/openvasmd/global_report_formats/a994b278-1f62-11e1-96ac-406186ea4fc5/generate /tmp/openvasmd_3scjKd/report.xml > /tmp/openvasmd_3scjKd/report.out 2> /dev/null md main: DEBUG:2014-12-22 13h27.28 UTC:13452: report_severity: max(severity)=9.3 md main: DEBUG:2014-12-22 13h27.29 UTC:13452: command: /bin/sh /usr/share/openvas/openvasmd/global_report_formats/a994b278-1f62-11e1-96ac-406186ea4fc5/generate /tmp/openvasmd_LiNI0X/report.xml > /tmp/openvasmd_LiNI0X/report.out 2> /dev/null md main:WARNING:2014-12-22 13h27.29 UTC:13452: read_from_client: failed to read from client: The TLS connection was non-properly terminated. lib serv:WARNING:2014-12-22 13h27.29 UTC:13452: Failed to gnutls_bye: Error in the push function. --- Below is the output from running the "" script: openvas-check-setup 2.2.6 Test completeness and readiness of OpenVAS-7 (add '--v4', '--v5', '--v6' 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 4.0.5. OK: OpenVAS Scanner CA Certificate is present as /var/lib/openvas/CA/cacert.pem. OK: NVT collection in /var/lib/openvas/plugins contains 37302 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 37310 files for 37302 NVTs. Step 2: Checking OpenVAS Manager ... OK: OpenVAS Manager is present in version 5.0.7. 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 123. OK: OpenVAS Manager expects database at revision 123. OK: Database schema is up to date. OK: OpenVAS Manager database contains information about 37302 NVTs. 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 5.0.3. Step 5: Checking OpenVAS CLI ... OK: OpenVAS CLI version 1.3.1. 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 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: Greenbone Security Assistant is running and listening on all interfaces. OK: Greenbone Security Assistant is listening on port 9392, which is the default port. Step 8: Checking nmap installation ... WARNING: Your version of nmap is not fully supported: 6.47 SUGGEST: You should install nmap 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. OK: SELinux is disabled. It seems like your OpenVAS-7 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. --- Thanks in advance, Traiano _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
