Re: Core dump on os_fingerprint.nasl

FYI, there were two parts to solving the problem.  I had to reduce the
size of the log files, as George suggested.  The issue was then to see
why the files got so big.  It turns out that one of our automated scans
was running all of the plugins rether than the few configured in the
nessusrc.  I never did figure out why, but I rebuilt the nessusrc from
scratch in the nessus GUI and had no more problems.

Beirne

Beirne Konarski wrote:
> George A. Theall wrote:
>
> > On Tue, Apr 19, 2005 at 09:58:03AM -0400, Beirne Konarski
> > wrote:
> >
> >
> >
> > > Core was generated by `nessusd: testing some_hostname'.
> > > Program terminated with signal 25, File size limit
> > > exceeded. 
>
>
> > Check the sizes on nessusd.messages / nessusd.dump -- one of
> > them exceeds 2GB, I suspect.
>
>
> That fixed the core dump problem.  I now just have the problem where the
> master nessusd just
> dies without leaving a core dump.  I don't have any additional
> diagnostics on this one but
> would appreciate any advice.
>
> Beirne
>
>
> > George
> >
> > --
> > theall@tenablesecurity.com
> > _______________________________________________
> > 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
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus