<nessus debug output removed> I have duplicated the problem that you are seeing. I am still trying to figure out what triggers the crash (ie. why it works sometimes).
I sent an e-mail to Victor (author of NessusWX) with details on how to reproduce the crash. As a workaround, if you use a detached scan NessusWX should perform the scan correctly. --Keith -----Original Message----- From: Young, Keith [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 11:01 AM To: Regalado, Ron Cc: [EMAIL PROTECTED] Subject: RE: Nessus 1.3.3 is out I am running NessusWX 1.4.2 now with Nessus 1.3.3 and it is working fine in both "normal"/detached mode. What is being logged to /usr/local/var/nessus/logs/nessusd.*? --Keith Young -----Original Message----- From: Regalado, Ron [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 12:48 PM To: [EMAIL PROTECTED] Subject: RE: Nessus 1.3.3 is out Is Nessuswx 1.4.2 compatible with the new version..? I just upgraded to Nessusd 1.3.3 and when I start a scan nessuswx just exits.. Ron -----Original Message----- From: Renaud Deraison [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 29, 2003 5:39 PM To: [EMAIL PROTECTED] Subject: Nessus 1.3.3 is out I'm pleased to announce the availability of Nessus 1.3.3. Nessus 1.3.x is still labelled as 'UNSTABLE', however, there's no showstopper bug I'm aware of, so you might want to give it a try. Note that in theory, it should be more gentle with your network, as well as faster. What is new in Nessus 1.3.3 : - The 'nessusd' process now takes very little memory, as plugins descriptions are now stored in a separate file which is loaded when necessary. As a side effect, nessusd now loads in no time (as it only parses the plugins which have changed), which make the calls to nessus-update-plugins less costly CPU-wise - Fixed the new plugins scheduler - if the optimizations were enabled, then the scan would hang (the error was really stupid). I also improved it and made it more gentle CPU-wise (although this can be improved even more). Note that given the way the nessusd <-> client communication is done and the way this scheduler works, it's no longer possible for the client to accurately display the name of the plugin which is being run. That might change in the future, but at this time, don't rely on the names displayed in the progress bar. (I think I'll remove this feature completely, as it makes no real sense to show the name of the plugins when they run in parallel anyway) - find_services.nes is now much faster, because it forks and divides the work between its children. - Various performance fixes / bugs fixes / minor improvements and all. I'm really happy with this release. If things go as smoothly as they've went so far, I may release Nessus 1.4.0 in a couple of releases. So please test it, and report any bug / annoyance you may find (yes, I'll start ironing things out now). Get it at http://www.nessus.org/experimental.html -- Renaud
