OK,
I found the problem. Some of the DNS servers that I was using wasn't reporting www.nessus.org correctly. Once I got that resolved it is working now. That brings up another question, shouldn't that have been reported?
Here is a snip from nessus-update-plugins script.
fetch_cmd="/usr/bin/wget -O -"
gzip=/bin/gzip }
If I removed the -q from the wget command it tells me what my problem is. I didn't notice and maybe I overlooked it but I didn't see an error trap in the script. Maybe just leaving the wget command without the -q solves the problem or at least tells you what is going on. On the plus side when it does work it tells you the progress of the download. I guess the only issue would be running it as a cron job.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 06, 2002 7:39 AM
To: Holmes, Tyran
Cc: Christopher Lyon; [EMAIL PROTECTED]
Subject: RE: Issues with nessus-update-plugins
I think I've seen this when the script has a problem downloading the .gz
file--make sure you can see nessus.org and the script can dowload the plugins.
the -l option will list out the plugins available.
-Sullo
Quoting "Holmes, Tyran" <[EMAIL PROTECTED]>:
> I wonder if recompiling it would help. I've never seen this before,
> however.
>
>
> -----Original Message-----
> From: Christopher Lyon [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 06, 2002 12:37 AM
> To: '[EMAIL PROTECTED]'
> Subject: Issues with nessus-update-plugins
>
>
>
> Any ideas of why I could be getting this?
>
> [root@localhost plugins]# nessus-update-plugins
>
> gzip: stdin: unexpected end of file
> cp: cannot stat `*.nasl': No such file or directory
> cp: cannot stat `*.inc': No such file or directory
> [root@localhost plugins]#
> [root@localhost plugins]#
>
>
>
> I have built a few of these machines and until now I haven't had a
> problem.
>
>
