On 2015-02-26 17:52, Win Pham wrote:
See if this helps:
[Thu Feb 26 17:45:39 2015][1490] Loading
2011/gb_google_chrome_mult_vuln_jun11_win.nasl
[Thu Feb 26 17:45:39 2015][1490] Loading
2011/gb_wireshark_asn1ber_dissector_dos_vuln_win.nasl
[Thu Feb 26 17:45:39 2015][1490] Loading
2011/gb_ubuntu_USN_1207_1.nasl
[Thu Feb 26 17:45:39 2015][1490] Loading
2011/openvas_tcp_scanner.nasl
[Thu Feb 26 17:45:39 2015][1490] received the SEGV signal
[Thu Feb 26 17:45:39 2015][1490] closing logfile
*
*
*
Hi,
I tried a clean rebuild with both OpenVAS 7 and 8, using the latest nvt
feed, and got no problems.
Can you get me a backtrace of the hanging process, using gdb ?
$ gdb -q
(gdb) attach PID_OF_OPENVASSD
<some output>
(gdb) bt
<post back this output>
On 2/26/2015 12:24 PM, Michael Meyer wrote:
*** Helmut Koers wrote:
md otp:MESSAGE:2015-02-26 16h32.24 CET:3476: Scanner loading: 38150
/
41904 nvts.
md otp:MESSAGE:2015-02-26 16h35.14 CET:3487: Scanner loading: 38150
/
41904 nvts.
md otp:MESSAGE:2015-02-26 16h35.14 CET:3488: Scanner loading: 38150
/
41904 nvts.
md otp:MESSAGE:2015-02-26 16h35.24 CET:3491: Scanner loading: 38150
/
41904 nvts.
Stop scanner and add "log_plugins_name_at_load = yes" to
/etc/openvas/openvassd.conf.
Start scanner and look in /var/log/openvas/openvassd.messages on
which NVT it hangs. Please try a few times to see if it is always
the
same NVT.
Micha
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
