On Thu, Apr 14, 2005 at 08:37:24AM -0400, Kaplan, Andrew H. wrote: > When I ran the automated scan this morning, the following > output was observed: ... > nessus: nessusd abruptly shut the communication down - the > test may be incomplete
You're seeing SIGSEGV's in nessusd.messages, right? > The nessus-update-plugins script was run last night, as > part of a nightly schedule, and was completed prior to the > above mentioned automated scan. There are two scans > which run nightly, and both generated the same output. Nicolas and I are looking into the problem. At the moment, there seems to be a problem with smb_nt_ms02-005.nasl which was updated yesterday and now causes the processes forked by nessusd to handle a client connection. Removing it from the plugins directory and then restarting nessusd appears to be a workaround. Hopefully we'll have a better solution soon. George -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
