Re: (ASCEND) Pipeline 50 V 6.0.2 resetting frequently

["Florian Sauer" <florian.sauer@musaion.de>]

Klaus,

thanks to your information we were finally (after 4 months of hassle) able
to solve the p50 reset problem.

We confirm that the problem is a memory leakage. In diagnostic mode, type

 pools

and

pool -s

That gives you information about memory usage.
When we did this each 1/2 hour we could see how the FREE MEMORY amount
would drop more and more. When it was about only 30kB we could be shure
that the pipeline would reset 2 minutes later.

> 
> Same problem with 5.1A, 5.1Ap9 (both b.p50 and bi.p50) and 6.0.2.
> The last stable version (uptime over 40 days) is the 5.0Ap33.

So what we did is load this software version 5.0App33. Since then the p50
has been up (1 day 15 hours) which never happened before with all the other
software versions we tried.

 
> Ascend EMEA support tells me not to use any version above 5.0
> (ticket number 263687) so I try to use only 5.0Ap33 until I read
> in a Release Note that memory leaks in filters are fixed.

After all, this is what we are going to do, too ...

A ticket number of us is still pending at Ascend EMEA support.

> 
> Ciao
>     Klaus
> 

Ciao and thanks again,


Florian

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

---

• Prev by Date: Re: (ASCEND) Access Control
• Next by Date: Re: (ASCEND) Access Control
• Prev by thread: Re: (ASCEND) Pipeline 50 V 6.0.2 resetting frequently
• Next by thread: (ASCEND) Routing outbound calls with 2 Maxen
• Index(es):
  • Main
  • Thread