Re: (PM) ComOS 4.1b15 Memory leak ?

Pavan Kumar (pkumar@ra.lucent.com)
Wed, 14 Apr 1999 11:08:30 -0700

Hi Folks,
Its not a memory leak. This chunk of memory is used to store call
accounting statistics. It should not grow beyond 5.0 MB as thats the max we
allocate depending on the call traffic to the box. Also, it will not affect
the normal operation of the System Manager Module.

Regards
Pavan Kumar
At 11:22 AM 4/14/99 -0500, Chris Parker wrote:
>At 10:48 AM 4/14/99 +0000, Paul Gregg wrote:
>>In article <37135514.8E22A813@livingston.com> you wrote:
>>> Paul Gregg wrote:
>>
>>>> The memory available appears to be dropping very slowly:
>>
>>> Memory usage will take a while to stabilize as more ports and features are
>>> used. If it continues to drop after a day or more of use then there
may be
>>> a problem.
>>
>>I think there is definately a problem now:
>
>Nope, I think there isn't. I thought there was too, and I saw the same
>behaviour on all on my PM-4's. A quick glance at the 'show mem verb'
>output tells you where it's all going.
>
>>pm1> ver
>>Lucent PortMaster PM-4 ComOS 4.1b15
>>System uptime is 1 days 9 hours 8 minutes
>>See end of this message.
>>
>>I'm gonna reboot the box to free up 6Mb before it runs out.
>
>It won't run out, rebooting is not needed, and will not actually
>fix anything.
>
>> ID Alloc Free In-Use Size Bytes Used Name
>>--- ------- ------- ------- ----- ---------- --------
>
>[ snip ]
>
>>176 153000 72725 80275 258 4819360 SNMP_BILLING
>
>Note that this chunk is using ~5 MB of memory. As to exactly what
>it is storing, I can't say ;) . I did call to report this already,
>and was informed that it is normal, and it will not run the box out
>of memory. For that matter, we were seeing problems in 4.0.3 where
>RAD_ACCT_BUF ( the radius accounting info buffer ) would fill up and
>lock the box solid. I've been told that the memory allocation/managment
>in 4.1b15 is much smarter and won't blindly allocate memory until it's
>gone.
>
>I would definitely call support though, as they can probably tell you
>a little more as to what all that memory is being used for. But it
>is supposed to do what it's doing. Here's one of my boxes:
>
><--paste-->
>
>lvchi4-1> ver
>Lucent PortMaster PM-4 ComOS 4.1b15
>System uptime is 19 days 14 hours 13 minutes
>lvchi4-1> sh mem
>System memory 17825536 bytes - 11693020 used, 6132516 available
>432:1 1056:0 4288:0 608:0 75616:0 112240:0 448:1 416:1 640:1 560:2 384:1
>368:1 1
>168:2 320:3 400:1 336:2 352:2 176:3 304:48 144:95 240:70 288:80 192:2 256:9
>96:1
>3 112:5 224:71 272:10 208:9 80:767 544:5 2048:1 4240:3 128:231 576:9 32:49
>48:92
> 20:555 64:4 1664:2 4096:2 160:8 16:154
>System nbufs 920 - 116 used, 804 available
>System blocks 460 - 50 used, 410 available
>lvchi4-1>
>
><--paste-->
>
>-Chris
>--
> \\\|||/// \ Chris Parker \ Systems and Network Engineering
> \ ~ ~ / \ StarNet, Inc. \ http://www.starnetusa.net
> | @ @ | \ (847)963-0116 \ mailto:cparker@megapop.net
>oOo---(_)---oOo--\------------------------------------------------------
> TANSTAAFL \ Wholesale Internet Services - http://www.megapop.net
>
>-
>To unsubscribe, email 'majordomo@livingston.com' with
>'unsubscribe portmaster-users' in the body of the message.
>Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>
>
>

-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>