On Fri, Jun 18, 2004 at 05:28:27PM +0100, Brian Jameson wrote: > If I run nessus from the command line with the following command:- ... > it works perfectly. If I use the same command in a script or in cron as root > then 99.99 times out of a 100 it fails with 'nessus : Could not open a > connection to the remote host'.
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 -- [EMAIL PROTECTED]
pgpz4HFFNfQgV.pgp
Description: PGP signature
_______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
