I too am having trouble with nessus-update-plugins failing, running version 2.2.6 of Nessus. I've got it running from cron once a day at about 8pm local time (GMT +0100), and it has only succeeded once in the last few weeks - on Sunday 9th if that makes any difference. I've turned on the -vv option to try and get more detail, but it doesn't help much.
Sometimes it fails at this stage: + /usr/local/bin/nessus-fetch --plugins-md5 More often at this stage: + /usr/local/bin/nessus-fetch --plugins [22570] plug_set_key:internal_send(0)['3 /tmp/ConnectTimeout/TCP/443=1; ']: Socket operation on non-socket Could not open connection to plugins.nessus.org - Socket operation on non-socket + echo 'Could not retrieve the Nessus plugins' Could not retrieve the Nessus plugins + echo Aborting Aborting + exit 1 It leaves behind it in the /tmp directory all-2.0.tar.gz.md5 and an empty all-2.0.tar.gz. If it fails at the earlier stage the error message is almost identical and I'm left with just an empty md5 file. Is this simply that I'm connecting at a time which is too busy and nessus-fetch is handling the timeout badly? Can you suggest a better time? -- Eleanor Blair [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
