George-

I re-downloaded the scripts this morning, and made the following
changes to update-nessus-plugins:

Updated the $ENV{PATH} with "/opt/nessus/sbin" (line 161)

Line 183 added / changed the my $plugins_dir to
"/opt/nessus/lib/nessus/plugins"

I have placed the following scripts in the directory:

"/opt/nessus/auto"

update-nessus-plugins
describe-nessus-plugin

********************

When I executed the update-nessus-plugin script with the following
command this morning:

"sudo perl -T /opt/nessus/auto/update-nessus-plugins -bps >
/home/cashby/plugin-report.txt"

I received this error:
Can't open 'W32.Sasser.Worm.nasl' - No such file or directory at
/opt/nessus/auto/update-nessus-plugins line 317

Reviewing the script it appears to fail after the plugins have been
updated and the 2nd round of MD5 hashing is taking place, with leads
me to believe that the script is having difficulties creating a new
MD5 of newly downloaded or changed plugins??? (probably way off base
here?)

Obviously the plugins are being updated because if the script runs
again I receive this message after it's completed:

"No errors found parsing new / changed plugins."

Am I possibly doing something wrong?  Thanks for any assistance...

ashby



On Mon, Dec 8, 2008 at 3:58 PM, George A. Theall
<[EMAIL PROTECTED]> wrote:
> On Dec 6, 2008, at 11:10 AM, christopher ashby wrote:
>
>> The 1st script (update-nessus-plugins.pl) executes properly and
>> updates the plugins, creates the MD5, and archives everything
>> according to plan.  When this scripts executes the
>> describe-nessus-plugin.pl script, it gives me an error saying that the
>> ""plugin isn't available??
>
> Is that the exact error? The string "plugin isn't available" doesn't
> exist as far as I can see in either script.
>
> One possible problem is that you've appended ".pl" to the name of each
> script. Neither is distributed that way, and it's not a big deal. But
> if you're going to change the name of describe-nessus-plugin, you need
> to make sure you update nessus-update-plugins to use the new name
> (line 352) .
>
> George
> --
> [EMAIL PROTECTED]
>
>
>
> _______________________________________________
> Nessus mailing list
> Nessus@list.nessus.org
> http://mail.nessus.org/mailman/listinfo/nessus
>
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to