George wrote... >This can happen when nessusd refuses the connection because, say, it's >too busy. For example, if your cron jobs run shortly after >nessus-update-plugins, you'll see this because nessusd is busy reloading >itself and rereading all the plugins. So the question is, what's >nessusd doing when you get these errors? > >George
George you've it the nail right on the head. I was running nessus-update-plugins and then kicking off nessus if their were any new .nasl files. Placing a 'sleep' command before the nessus command has solved the problem. Thank you. regards, Brian _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
