Hi All [Using openVAS 6, installed from the atomic repos. On CentOS 6.5]
I'm running a scan initiated from a master node to a slave node. From the masters perspective the scan seems to die at 3% consistently, with the following messages in the master's logs. However, the scan continues on the slave! Master openvasmd.log entries related to the scan task: --- event task:MESSAGE:2014-10-18 14h13.00 UTC:4086: Status of task scan-range-192.168.0 (xxxxx-xxxx-xxx-xxxxx) has changed to Requested event task:MESSAGE:2014-10-18 14h13.00 UTC:4086: Task xxxxx-xxxx-xxx-xxxxx has been requested to start by admin event task:MESSAGE:2014-10-18 14h13.27 UTC:4088: Status of task scan-range-192.168.0 (xxxxx-xxxx-xxx-xxxxx) has changed to Running event task:MESSAGE:2014-10-18 14h33.05 UTC:4088: Status of task scan-range-192.168.0 (xxxxx-xxxx-xxx-xxxxx) has changed to Internal Error md main:CRITICAL:2014-10-18 15h05.13 UTC:5192: handle_sigsegv: segmentation fault --- Traces from log on slave at around this time: --- ==> /var/log/openvas/openvasmd.log <== . . md main:WARNING:2014-10-18 14h34.43 UTC:16730: read_from_client: failed to read from client: The TLS connection was non-properly terminated. lib serv:WARNING:2014-10-18 14h34.43 UTC:16730: Failed to gnutls_bye: Error in the push function. --- And there appear to be regular SIGSEGV errors in the openvassd logs on the slave during the scan process: --- [Sat Oct 18 14:35:19 2014][20293] SIGSEGV occured ! [Sat Oct 18 14:35:19 2014][20293] closing logfile [Sat Oct 18 14:35:19 2014][22681] Process 20293 seems to have died too early --- Is there a known cause for this kind of behavior, and how would I go about troubleshooting this further? Thanks in advance! Traiano _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
