On 5 Sep 2002, Kristofer T. Karas wrote: > Running tcpdump showed no network activity from nessusd. Top showed > each nessusd thread stuck in a tight run loop. Strace showed the only > system call being executed was brk(0x.....) roughly once every second or > two.
The alleged current plugin displayed bu the GUI is not very accurate (esp. when multiple plugins are started in parallel), you need to check the log to determine what plugin is run by the stuck process or whether the stuck process is a master process. You can also attach gdb to the stuck process and use gdb commands to examine its state. And do not forget to check nessusd.dump--processes spinning in a loop do often generate tons of error messages. --Pavel Kankovsky aka Peak "Welcome to the Czech Republic. Bring your own lifeboats." - [EMAIL PROTECTED]: general discussions about Nessus. * To unsubscribe, send a mail to [EMAIL PROTECTED] with "unsubscribe nessus" in the body.
