Hi, A friend of mine show me that latest feed contains lots of duplicate plugins (we count 3952).
example: /var/lib/openvas/plugins/openvas_tcp_scanner.nasl /var/lib/openvas/plugins/2011/openvas_tcp_scanner.nasl this causes openvassd 6 to crash (coredump) on few duplicate (5 plugins) during plugins loading. Perhaps Older version than latest Openvas 7/8 may shared same behaviour. To fix, We run a script to delete duplicates after nvt-sync. BR Seb 2015-02-26 20:35 GMT+01:00 Win Pham <w...@mindspring.com>: > > We just finished a clean build and you're right that it does fix the > issue. From that, it is clear the issue was address in the openvas code > already. > > I think the issue will only affect folks who have older versions of > Openvas as we did on a few boxes. One of the boxes was running the 7 > beta. It's interesting that the .nasl while loading could cause the SEGV > signal to be received (as logged) and discontinue loading the rest. Below > is the gdb from the beta7. I just didn't loading a .nasl would ever cause > an issue. > > (gdb) bt > > #0 0x00007f68a5405060 in recvmsg () at > ../sysdeps/unix/syscall-template.S:83 > > #1 0x00000000004076b1 in loading_handler_start () > > at /opt/download/openvas-scanner-4.0+beta7/src/openvassd.c:749 > > #2 main (argc=1, argv=0x7fffe2205cd8) > > at /opt/download/openvas-scanner-4.0+beta7/src/openvassd.c:950 > > > > > > > On 2/26/2015 1:17 PM, Hani Benhabiles wrote: > > 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 > Openvas-discuss@wald.intevation.org > > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss@wald.intevation.org > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss > > > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss@wald.intevation.org > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss > -- -- Sébastien AUCOUTURIER | Research and Development Manager Phone. +33(0)5.67.34.67.84| www.itrust.fr IT Security Experts (Services & Solutions) | Keep Information Security Simple This e-mail is confidential (and any attachments) is intended to its recipient(s).
_______________________________________________ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
