Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IPO Server Edition 9.1.4 restart - Abnormal Termination 2

Status
Not open for further replies.

dibthree

Technical User
May 3, 2006
398
US
IPO Server Edition 9 Release 9.1.4 Server Edition

System rebooted.

Termination Casue: <Segmentation violation> addr=00000000 d=4294967294 pc=00000000 00000000 00000000 00000000 940bf488

Any idea what this means?
 
Nope. And unless it does it more than once you shouldn't care either.

Stuck in a never ending cycle of file copying.
 
The system is big for an IPO - about 1200 phones. The powers that be get wound up about any down time.

I was tasked with finding out what happened and why. I was hoping for a power event - not so lucky.

From what I have been reading looks like this is a known bug. It looks like the issue was addressed in 9.1.11.

IP Office Technical Bulletin 205:
IPOFFICE-120818 System Restart - Server Edition: System Reboot with Abnormal Termination

Now the real question is does the patch resolve the issue.
 
You will only find out by upgrading it.

BAZINGA!

I'm not insane, my mother had me tested!
 
There's a lot of reboot bugs fixed from 9.1.4 to 9.1.12.

First release that we used on customers on a large scale was 9.1.6 since there were issues before that.

"Trying is the first step to failure..." - Homer
 
If the power that be are so exercised by downtime then they can pay for a proper support contract rather than coming to an free internet forum.

The system has a watchdog function which, if it thinks something has gone wrong (run out of memory, stuck in a loop, whatever), will restart the switch. You want that rather than coming in in the morning and finding everything stopped. However, that does mean that every release and service pack includes a number of "System Restart with Abnormal Termination" fixes - but not necessarily yours unless was repeatable on other systems.

The information (the addr=00000000 d=4294967294 pc=00000000 00000000 00000000 00000000 940bf488 bit) gives Avaya some idea of where the system was in its code when the issue occurred but only they can interpret that and its only a clue. So unless its an issue they've already seen on other systems, they would want traces and other info and would probably ask for an upgrade to the latest Service Pack before the issue got anywhere near the support level where they can read the address codes).




Stuck in a never ending cycle of file copying.
 
Also as R11 is released 9.1 is no longer supported, so if a later service pack doesn't fix it you need to go to at least R10 to get support.

"Trying is the first step to failure..." - Homer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top