Abnormal Termination Error After Sporadic Reboot: IP500 V2 8.1 (73)

[nickgall]

From what we can tell so far, a few times since December 11 2014, our phone server appliance reboots; on seemingly random Thursdays (not at the same time of day, not each Thursday of the week). We haven't done anything to that box in quite awhile; no server updates, etc. Everything we've done has been through Manager, VM Pro, and the like.

SSA Viewer gives us:

Date: 12/11/2014 9:43:14 AM
Reason: Abnormal Termination
Termination Cause: <TLB Data > addr=36372e31 d=5 pc=f13f7130 stack=f030daa0 f0ab477c f0abaf54 f0abb780 f0abb954

The last Abnormal Termination Cause I have from 01/22/15 is very much similar to the one above; <TLB Data > addr=33372e47...

I don't see much information anywhere on this Cause, and we think it's pretty useless, which seems to be the norm with these. So, we turned on SysMonitor, and patiently waited. Here's what we have just before the last Event:

-----------------------------------------------------------------------------------------

2015-01-22T01:27:18 1149012565mS H323Evt: Recv: RegistrationRequest 172.119.0.12; Endpoints registered: 47; Endpoints in registration: 0
2015-01-22T01:27:18 1149012565mS RasTx: v=Src=172.16.0.3:1719, Dst=172.119.0.12:49305 peb=0
RasMessage = registrationConfirm

2015-01-22T01:27:18 1149012710mS RES: Thu 22/1/2015 01:27:20 FreeMem=54229356 51924916(1) CachedMem=2304440 CMMsg=11(11) Buff=5200 1203 1000 12478 4 Links=24801 BTree=0 CPU=1/3/5212/33063/49211/1
2015-01-22T01:27:18 1149012710mS RES2: IP 500 V2 8.1(73) Tasks=46 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=145 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=3 SSA=0 TCP=254 TAPI=1 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
2015-01-22T01:27:18 1149012711mS RES4: XML MemObjs=45 PoolMem=2097152(1) FreeMem=2082064(1)
2015-01-22T01:27:18 1149012740mS RasRx: v=IFace=LAN1, Src=172.117.0.12:49305, Dst=172.16.0.3:1719 peb=0
RasMessage = registrationRequest

2015-01-22T01:27:18 1149012740mS H323Evt: Recv: RegistrationRequest 172.117.0.12; Endpoints registered: 47; Endpoints in registration: 0
2015-01-22T01:27:18 1149012741mS RasTx: v=Src=172.16.0.3:1719, Dst=172.117.0.12:49305 peb=0
RasMessage = registrationConfirm



-----------------------------------------------------------------------------------------

Two seconds later, the logging resumes with a fresh SysMonitor connection.

Here's some of the other threads I've looked at that may be helpful/refreshing when researching this issue:

thread940-1724318 has a setup similar to this

thread940-1705281 has a problem similar to this

We appreciate any help and insight anyone can give!

 

[intrigrant]

I don't think these kind of problems can be solved here, you need Avaya support but they don't do 8.1 anymore and they will ask you to upgrade to the latest GA before any investigation will be done.
The error can be in monitor but it may well be some time earlier as the last part of the reboot logged as the internal watchdog tries to solve the problem before the reboot takes place.

 

[holdmusic34]

And those people that don't come back and close off threads with resolutions are extremely annoying. The site is about solutions to problems. Fact is, ultimately people ending up most times solving the problem on their own. It's nice when people have the courtesy to explain what happened in their situation.

You lose, Carl Miller.

 

[nickgall]

Thanks guys.

I see a couple service packs available that are above what we're running, that might address this issue, the latest one from about a month ago. It doesn't make sense that they'd do Service Packs but not support 8.1 anymore. So, I'll peek at the documentation and go from there.

I don't see a way to close this thread.

 

[derfloh]

They don't support R8.1 since GA of 9.1.

Avaya only supports the actual and previous release.

 

[korexxkun]

Im using an Avaya IPO Server Edition 9.1 and im having similar trouble. Its been running for about a month and half now. This has been occurring for like a week now. Are there service packs available to tackle issue. Ive already raised a ticket with Avaya though

 

[nickgall]

korexxkun,

Our upgrading to 9.1 seemed to solve our trouble; it has yet to come back. I've also seen one service pack come out from Avaya, though I don't know that it'll address your trouble. Also, they have a second service pack coming out within the next day or two, if it isn't out already.

In my humble opinion, I'd stick with Avaya support on this one.