Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Nessus: devel

plugins can't allocate memory

 

 

Nessus devel RSS feed   Index | Next | Previous | View Threaded


thomas at intevation

Dec 21, 2004, 4:52 AM

Post #1 of 10 (2152 views)
Permalink
plugins can't allocate memory

Hi!

While scanning with plugins from CVS HEAD many errors show up in
nessusd.dump:

[12114] Could not allocate a pointer of size 25 !
[12115] Could not allocate a pointer of size 131073 !
malloc: Cannot allocate memory
Could not realloc() a pointer of size 87361 !
mmap : Cannot allocate memory

$ grep alloc nessusd.dump|wc -l
1636

There is enough memory available in the system.

libnasl/nessus-libraries/nessus-core/plugins from today's CVS on
Debian woody.

Older plugins work fine, even used with everything else from HEAD.

At least one other person is experiencing the same problems.

Thomas

--
Email: thomas [at] intevation
http://intevation.de/~thomas/


thomas at intevation

Dec 21, 2004, 10:46 AM

Post #2 of 10 (2091 views)
Permalink
Re: plugins can't allocate memory [In reply to]

* Thomas Arendsen Hein <thomas [at] intevation> [20041221 12:53]:
> While scanning with plugins from CVS HEAD many errors show up in
> nessusd.dump:
>
> [12114] Could not allocate a pointer of size 25 !
> [12115] Could not allocate a pointer of size 131073 !
> malloc: Cannot allocate memory
> Could not realloc() a pointer of size 87361 !
> mmap : Cannot allocate memory
>
> $ grep alloc nessusd.dump|wc -l
> 1636
>
> There is enough memory available in the system.
>
> libnasl/nessus-libraries/nessus-core/plugins from today's CVS on
> Debian woody.
>
> Older plugins work fine, even used with everything else from HEAD.

FYI: Everything from 2.2 branch and plugins from 20041201 yield the
same problems.

Thomas

--
Email: thomas [at] intevation
http://intevation.de/~thomas/


deraison at nessus

Dec 21, 2004, 11:38 AM

Post #3 of 10 (2076 views)
Permalink
Re: plugins can't allocate memory [In reply to]

On Tue, Dec 21, 2004 at 12:52:49PM +0100, Thomas Arendsen Hein wrote:
> Older plugins work fine, even used with everything else from HEAD.

Do you have any other details on your setup, like the scanning options
or anything which could be a bit useful for your "report" ?


Thanks,
-- Renaud


thomas at intevation

Dec 21, 2004, 1:36 PM

Post #4 of 10 (2100 views)
Permalink
Re: plugins can't allocate memory [In reply to]

* Renaud Deraison <deraison [at] nessus> [20041221 19:39]:
> On Tue, Dec 21, 2004 at 12:52:49PM +0100, Thomas Arendsen Hein wrote:
> > Older plugins work fine, even used with everything else from HEAD.
>
> Do you have any other details on your setup, like the scanning options
> or anything which could be a bit useful for your "report" ?

Everything default, i.e. removing ~/.nessus and ~/.nessusrc,
starting the HEAD GUI, new task, new scope, execute.

There is a result, but only 9 instead of 22 notes, 4 instead of 21
warnings and 2 instead of 8 holes found.

Test system is Debian woody 3.0r3 with many services enabled.
Nessus client and server are running on the same machine.

Nessus things are compiled with --enable-debug (except plugins).

So I think there's nothing special in my setup.

Thomas

--
Email: thomas [at] intevation
http://intevation.de/~thomas/


deraison at nessus

Dec 21, 2004, 1:47 PM

Post #5 of 10 (2102 views)
Permalink
Re: Re: plugins can't allocate memory [In reply to]

On Tue, Dec 21, 2004 at 09:36:37PM +0100, Thomas Arendsen Hein wrote:
> > Do you have any other details on your setup, like the scanning options
> > or anything which could be a bit useful for your "report" ?
>
> Everything default, i.e. removing ~/.nessus and ~/.nessusrc,
> starting the HEAD GUI, new task, new scope, execute.


Delete /usr/local/lib/nessus/plugins/.desc/ as well.

> There is a result, but only 9 instead of 22 notes, 4 instead of 21
> warnings and 2 instead of 8 holes found.
>
> Test system is Debian woody 3.0r3 with many services enabled.
> Nessus client and server are running on the same machine.
>
> Nessus things are compiled with --enable-debug (except plugins).

That may also be an issue - I need to double-check that, but this option
has not really been used for a while on our side.


thomas at intevation

Dec 22, 2004, 12:26 AM

Post #6 of 10 (2095 views)
Permalink
Re: plugins can't allocate memory [In reply to]

* Renaud Deraison <deraison [at] nessus> [20041221 22:58]:
> Delete /usr/local/lib/nessus/plugins/.desc/ as well.

Always did that.

> On Tue, Dec 21, 2004 at 09:36:37PM +0100, Thomas Arendsen Hein wrote:
> > Nessus things are compiled with --enable-debug (except plugins).
>
> That may also be an issue - I need to double-check that, but this option
> has not really been used for a while on our side.

I nearly always used that and never had problems with it.

I investigated the problem a little bit: It was introduced with
adding plugins/nessus_tcp_scanner on November 21st. If I delete that
directory but installing everything else from HEAD, this problem
disappears.

Thomas

--
Email: thomas [at] intevation
http://intevation.de/~thomas/


mikhail at nessus

Dec 22, 2004, 2:59 AM

Post #7 of 10 (2089 views)
Permalink
Re: Re: plugins can't allocate memory [In reply to]

On Wed Dec 22 2004 at 08:26, Thomas Arendsen Hein wrote:

> I investigated the problem a little bit: It was introduced with
> adding plugins/nessus_tcp_scanner on November 21st.

Odd...

> If I delete that directory but installing everything else from HEAD,
> this problem disappears.

Are you still running a scanner then?


thomas at intevation

Dec 22, 2004, 3:27 AM

Post #8 of 10 (2101 views)
Permalink
Re: plugins can't allocate memory [In reply to]

* Michel Arboi <mikhail [at] nessus> [20041222 11:00]:
> On Wed Dec 22 2004 at 08:26, Thomas Arendsen Hein wrote:
> > I investigated the problem a little bit: It was introduced with
> > adding plugins/nessus_tcp_scanner on November 21st.
>
> Odd...
>
> > If I delete that directory but installing everything else from HEAD,
> > this problem disappears.
>
> Are you still running a scanner then?

With defaut settings I guess it's only the ping scanner, but I also
tried enabling other scanners and they work fine.

I even tried compiling everything without --enable-debug now, but
results are the same, even on a different test machine in another
network (but still Debian woody).

Thomas

--
Email: thomas [at] intevation
http://intevation.de/~thomas/


thomas at intevation

Dec 22, 2004, 4:18 AM

Post #9 of 10 (2095 views)
Permalink
Re: plugins can't allocate memory [In reply to]

* Thomas Arendsen Hein <thomas [at] intevation> [20041221 18:47]:
> * Thomas Arendsen Hein <thomas [at] intevation> [20041221 12:53]:
> > While scanning with plugins from CVS HEAD many errors show up in
> > nessusd.dump:
> >
> > [12114] Could not allocate a pointer of size 25 !
> > [12115] Could not allocate a pointer of size 131073 !
> > malloc: Cannot allocate memory
> > Could not realloc() a pointer of size 87361 !
> > mmap : Cannot allocate memory
> >
> > $ grep alloc nessusd.dump|wc -l
> > 1636
> >
> > There is enough memory available in the system.
> >
> > libnasl/nessus-libraries/nessus-core/plugins from today's CVS on
> > Debian woody.
> >
> > Older plugins work fine, even used with everything else from HEAD.
>
> FYI: Everything from 2.2 branch and plugins from 20041201 yield the
> same problems.

Very strange. I just compiled current 2.2 branch with current
plugins and the problem doesn't appear, but looking at logs from my
other tests, I really used 2.2 branch and plugins from 20041201 in
above test.

Using a HEAD client to connect to this 2.2 server works fine, too.

Very very strange ...
Thomas

--
Email: thomas [at] intevation
http://intevation.de/~thomas/


thomas at intevation

Dec 22, 2004, 5:36 AM

Post #10 of 10 (2100 views)
Permalink
Re: plugins can't allocate memory [In reply to]

* Thomas Arendsen Hein <thomas [at] intevation> [20041222 12:19]:
> * Thomas Arendsen Hein <thomas [at] intevation> [20041221 18:47]:
> > FYI: Everything from 2.2 branch and plugins from 20041201 yield the
> > same problems.
>
> Very strange. I just compiled current 2.2 branch with current
> plugins and the problem doesn't appear, but looking at logs from my
> other tests, I really used 2.2 branch and plugins from 20041201 in
> above test.
>
> Using a HEAD client to connect to this 2.2 server works fine, too.

I found the problem: The HEAD client doesn't set the following
SERVER_PREFS to their default values:

auto_enable_dependencies = yes
cgi_path = /cgi-bin:/scripts
port_range = default
continuous_scan = no
detached_scan = no
save_empty_sessions = no
save_session = no

An unset port_range leads to problems in the new nessus_tcp_scanner.

A quick grep over other parts of nessus shows that port_range really
never should be unset. Bad things will happen in the server.

For a quick solution I'll fix the client, but a better error
checking is really needed, or what do you think?

Thomas

--
Email: thomas [at] intevation
http://intevation.de/~thomas/

Nessus devel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.