[plug] Memory Alloc error?

[Ben Jensz]

When watching top while running the rpm process, it uses about 5% CPU usage
and about 0.4% of system memory and then stops.

The majority of the memory usage is "cached", so if an active process needs
the memory, it'll free up that memory.  I've got another machine setup which
is running a very similar configuration and its been up for 154 days now and
it hasn't had problems like this other one has (and its got about half the
system resources).

I haven't tried a reboot on the machine, but its only been up 11 days.


/ Ben

----- Original Message -----
From: "Graham, Alan A." <Alan.Graham at woodside.com.au>
To: <plug at plug.linux.org.au>
Sent: Tuesday, September 18, 2001 1:14 PM
Subject: RE: [plug] Memory Alloc error?


> Did you run Top while the rpm process was active?  Because it looks to me
> like you've got a major memory leak in some other process.  2Mb free isn't
a
> lot on a 512Mb machine.  If rpm wan't running when you ran top, then have
a
> look at where all the memory is being used.
>
> How long has this machine been up?  I hate to sound windoze'ish, but hav
you
> tried rpm after a reboot?  If it works, then I would suggest that points
> again to a memory leak.
>
> Alan
>
> > -----Original Message-----
> > From: Ben Jensz [SMTP:jensz at wn.com.au]
> > Sent: Tuesday, September 18, 2001 12:23 PM
> > To: plug at plug.linux.org.au
> > Subject: Re: [plug] Memory Alloc error?
> >
> > The machine is running kernel 2.2.19 (SMP capable, its a Dual PIII 500).
> >
> > The machine also has 512Mb of RAM in it.  The machine is running Apache,
> > Postfix, Squid and Samba as its main tasks.
> >
> > I mean I can compile libpcap and other stuff from source fine.  But
> > installing stuff from RPMs _should_ work.
> >
> > These are the memory stats from top:
> >
> > Mem:   517268K av,  514432K used,    2836K free,   69192K shrd,   39596K
> > buff
> > Swap:  787144K av,    1904K used,  785240K free                  356468K
> > cached
> >
> > It was installing RPMs fine before, but now its coming up with errors.
I
> > haven't changed anything recently that would affect RPM operations.
> >
> >
> > / Ben
> >
> > ----- Original Message -----
> > From: "Simon Scott" <simon.scott at flexiplan.com>
> > To: <plug at plug.linux.org.au>
> > Sent: Tuesday, September 18, 2001 12:03 PM
> > Subject: Re: [plug] Memory Alloc error?
> >
> >
> > > Sounds like either
> > >
> > > a) your kernel is broken somehow - which kernel are you running?
> > > b) You have hardware problems that is causing a malloc to fail - or
> > > perhaps, quite literally, the malloc is failing due to not enough
memory
> > > c) There is some broken version of rpm - but it looks like the
> > > malloc is failing, something beyond the application's control
> > >
> > > Are you running a swap partition?
> > >
> > > How much RAM have you got?
> > >
> > > What are you running on the box?
> > >
> > > What does 'top' say about memory?
> > >
> > >
> > >
> > >
> > > From: Ben Jensz <jensz at wn.com.au> on 18/09/2001 11:56 AM
> > > Please respond to plug at plug.linux.org.au@SMTP at Exchange
> > > To: plug at plug.linux.org.au@SMTP at Exchange
> > > cc:
> > >
> > > Subject: [plug] Memory Alloc error?
> > >
> > > Hey all,
> > >
> > > When I try to install the libpcap RPM, it comes up with this error:
> > >
> > > [root at dugong /root]# rpm -ivh libpcap-0.4-19.i386.rpm
> > > Preparing...                memory alloc (3663422781 bytes) returned
> > > NULL.
> > >
> > > This is on a Red Hat 6.2 system... the whole RPM system in general
> > > is acting
> > > really screwy at the moment on this system as well.
> > >
> > > Anyone got any thoughts?
> > >
> > > TIA
> > >
> > >
> > > / Ben
> > >
> > >
> > >
> > >
> > > **********************************************************************
> > > This email and any files transmitted with it are confidential and
> > > intended solely for the use of the individual or entity to whom they
> > > are addressed. If you have received this email in error please notify
> > > the system manager.
> > >
> > > This footnote also confirms that this email message has been swept by
> > > MIMEsweeper for the presence of computer viruses.
> > >
> > > www.mimesweeper.com
> > > **********************************************************************
> > >
> >
>