Danny Johnson was correct in that it was not a memory problem. Most
replies pointed to ulimit/limit and excessive logins. Neither was the
case. Several people asked how much memory was in the system; 4GB of RAM
and 1GB of swap. Not likely sar is going to eat up that much memory,
especially since swap -s showed 3GB still available.
But the Pint of Choice goes to John Dodge:
"This is a common problem, check your crontab entries and make sure you are
not running the /usr/lib/sa/sa1 script twice at the same time. typically
int the /var/spool/cron/crontabs/sys file there are two lines executing
the /usr/lib/sa/sa1 script so you need to make sure these are never
executing at the same time."
I looked and, sure enough, there they both were, running like little
hamsters. I commented one out, removed all the previous sa files (they
were no good anyway), and, so far, have good data that I can look at
without a malloc error.
Thanks also to:
Bob Dexter Kevin Sheehan
Sundar Paramasivam Bruce Zimmer
Dave Foster Birger Wathne
Brett Lymn Mike Salehi
Harvey Wamboldt Gary Franczyk
---------------------- Forwarded by Jeff Kennedy/NDS on 07/25/99 09:48 AM
"Jeff Kennedy" <firstname.lastname@example.org> on 06/23/99 03:39:40 PM
cc: (bcc: Jeff Kennedy/NDS)
Subject: malloc failed
I am trying to run sar on one of my servers but I keep getting the
sar: malloc failed
Not enough space
Originally I was trying it with sarcheck but that wasn't working so then I
tried it with sar. I get the same error in either case.
What space is it trying to use? I have checked my filesystems and the
lowest available space is / at 33MB avail. /tmp shows a little over 3GB
avail and swap -l shows the same. So, either way I should have enough
space, or at least enough in conventional terms.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:22 CDT