Re: [cobalt-developers] RaQ3 memory leak problems?

[Jeff Lasman <jblists@xxxxxxxxxxxxx>]

Michael Stauber wrote:

> > Our resolution will probably be to reboot the system with a cron-script
> > at 6:00 am every morning.  Does that sound reasonable to you?
> 
> Yes, it might help.

We didn't have to do it this morning; we made it through the
night/morning, and we're now at just under 14 megabytes of free memory
(the system total is 256 megabytes).

Here's the /proc/meminfo output:

<snip>
 [admin@bessie admin]$
         total:    used:    free:  shared: buffers:  cached:
 Mem:  263741440 249368576 14372864 81453056  9334784 202129408
 Swap: 134692864  1204224 133488640
 MemTotal:    257560 kB
 MemFree:      14036 kB
 MemShared:    79544 kB
 Buffers:       9116 kB
 Cached:      197392 kB
 SwapTotal:   131536 kB
 SwapFree:    130360 kB
 [admin@bessie admin]$
</snip>

> > In our case the problem was sendmail and a huge mailing list, but
> > nevertheless it worked fine until the nightly cron.daily scripts are
> > run.
> 
> Hmm ... Sendmail? That's interesting. Just for the records: Do you use MySQL
> on that server, too?

My typing got slightly ahead of my brain when I wrote that.  We were
running "subscribe me pro" which has been discussed on this list (or
perhaps cobalt-users) before.  It calls lots of sendmail processes, and
the sendmail "accepting" daemon changes into "denying" as memory
availability goes into the toilet.  At least that's the behavior I've
been seeing.  We actually no longer see "sendmail: accepting"; instead
we see "sendmail: denying" when we run ps aux.

> > Do you thinking upping this 256 Megabyte box to 512 will help?
> 
> In my case it extended the periods between required reboots, so I'd say it
> might gain you a little more time, roo.

Thanks.  We're going to go ahead and order it today.

Jeff
-- 
Jeff Lasman <jblists@xxxxxxxxxxxxx>
Linux and Cobalt/Sun/RaQ Consulting
nobaloney.net, P. O. Box 52672, Riverside, CA  92517
voice: +1 909 778-9980  *  fax: +1 909 548-9484