Hello George,

Wednesday, August 27, 2003, 9:26:41 PM, you wrote:

GT> On Tue, Aug 26, 2003 at 02:26:23PM -0400, [EMAIL PROTECTED] wrote:

>> When I type nessus-install-plugins I get the following error:

GT> You mean "nessus-update-plugins", right?

>> "something went wrong when installing the plugins - uncompressing the
>> plugins archive failed"
>> 
>> Where can I find an error log?  Any clues on what went wrong?

GT> Unfortunately, it's not easy to track down the problem.  You can try
GT> running it as "sh -x nessus-update-plugins" and/or editing the script to
GT> not delete the scratch directory when this error occurs so you can study
GT> the download.  But if you've been running this successfully in the past
GT> you'll probably find the problem is in retrieving the plugins. 

GT> I ran into this problem 2 weeks ago -- for several days the download
GT> failed consistently when run out of cron early in the morning.  I'd run
GT> it by hand and it would be fine.  So I modified the script as described
GT> above only to find the files downloaded via cron were always corrupt
GT> while the others were fine. 

GT> Thinking that perhaps my cron jobs just happened to be snagging the file
GT> as it was being updated, I modified my cron job to run the script
GT> several times each night.  Unfortunately, as soon as I did that the
GT> problem went away.  :-(

GT> George

My problem was near that, i ran "nessus-update-plugins -v" many times,
and after each try it reported me after getting all-2.0.tar.bz (or something like
that) "something went wrong when installing the plugins - uncompressing the
plugins archive failed" (the same as in the original letter). So i had
forgotten about this feature for a while. But now i'm have written
syntax parser for NASL2 (flex + yacc). And was testing plugins in
"/usr/local/lib/nessus/plugins/". I was amazed... Cause when i started
that script in this dir, everything worked just fine. But there were no
messages about downloading "all-2.0..." (probably i had downloaded it
before and stored somewhere). Then script displayed a list of plugins
(which had changed i suppose) and that's it. BTW, At the first time
i've launched script, it couldn't find "wget", but i've fixed one variable
full path instead of "wget" =).

Reply via email to