Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) Pipeline 50 V 6.0.2 resetting frequently

Florian Sauer wrote:

> > >  Looks like the Pipeline is having some sort of memory leak, or it
> > > can't free up resources.
> 
> > I thought something like that! I'm running 6.0.2 on a P50, and according
> > to my syslog, it resets hourly, but only if the connection isn't up.
> 
> Everybody whom I spoke to told me it's a memory leakage problem. That means
> it's in the software, not the hardware (as I said, we changed machines - no
> success).

This is software and I think this is really a memory leakage problem.
We had this with different Pipelines, differnt firmware, different locations.

> > If the connection is up, it'll run for days. In every other respect the
> > box works fine.
> 
> Yes, same with us. But we cannot afford having a connection all day long
> (telco costs in Germany are quite hight).

You say it: telco costs in Germany :-(
We use timeout=10 and so up to 300 call per day.

> We have some undefinable "noise" packets on the ethernet which I filtered
> out for call. Ascend support checked our machine via telnet and said there
> is nothing "unusual" in the setup of our machine. Maybe they haven't spent
> thoughts on the filter issue.

This seems to be the problem (our Pipelines use full Filter: 12 in / 11 out)
Dial out only for what really needed and we could use more filters.

> > My guess is those unforwarded packets are filling
> > up memory until it finally runs out and dies.
> 
> Sounds logical, could anyone confirm this?

IMHO Yes.

> > I'm going to try 5.1Ap9 as suggested. My box didn't do this before.
> 
> We ran 5.1 (it was in the unit when we bought it), and the symptoms were
> the same. Maybe we didn't have Ap9.

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.

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.

Ciao
    Klaus

BTW. Our Max has now UpTime: 258 days, 6 hours, 48 minutes, 19 seconds
Thats what I call stable.

--
Dipl.-Inform. Klaus Noack
Syscomp GmbH / Abteilung DFUE
August-Wessels-Strasse 5
D-86154 Augsburg / Germany
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>
Follow-Ups: References: