Get no answer error while configuring via mgr

[leo]

Hi All,
Need Advise on this:
System: R5.1.2-e2.504-1-h-c6s2
Whenever we attempt some configuration changes via mgr we get an error "get no answer" (attached error.jpg).
following incidents come up:
23/03/11 11:02:01 000002M|--/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 9831
23/03/11 11:02:04 000002M|--/--/-/---|=2:2650=SQL error: appli MAO_AGENT table No 2650 error -25000
pid 23095: Relaunch (sig 15)
pid 23100: Relaunch (sig 15)
pid 23098: Relaunch (sig 15)
pid 23094: Relaunch (sig 15)
pid 23092: Relaunch (sig 15)
23/03/11 11:02:05 000002M|--/--/-/---|=0:2663=IPC Chorus err: appli MAO_AGENT oper 30 err -1
23/03/11 11:02:20 000002M|--/--/-/---|=0:2663=IPC Chorus err: appli MAO_AGENT oper 30 err -1
23/03/11 11:02:20 000002M|--/--/-/---|=0:2663=IPC Chorus err: appli CALLHANDLING oper 6 err -7
Command "INTERNAL_TAX" (pid 23083) exited with status 162.
23/03/11 11:04:16 000002M|--/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 9831

Did the following:
1. System reboot and observed as below... incidents and exceptions:
Command "SQLSRV" (pid 748) exited with status 139.
Command "SQLSRV" (pid 806) exited with status 139.


======================
SIGSEGV
======================
Registers:
EFLAGS = 0x00010206
EAX = 0x213f2124
EDX = 0x213f2102
EIP = 0x400ec4d2
EDI = 0x400ec4d2
ESI = 0x213f2120
EBP = 0xbffff714
EBX = 0x40123ba0
ECX = 00000000

Backtrace :
Backtrace recurence: 0 pc:0x400ec4d2 ebp:0xbffff714
Backtrace recurence: 1 pc:0x400ec57c ebp:0xbffff7f4
Backtrace recurence: 2 pc:0x400ec18f ebp:0xbffff844
Backtrace recurence: 3 pc:0x40039390 ebp:0x00000000


2. Restored an ok old database , but still the issue prevails.

Could anything be done on this.

regards,
LEO

[sera544]

Hi,

I don't know this can solve ur issue..but try this procedure below..


Log on as “mtcl” on the console and enter the following command:
Xa00001> route add localhost xx.xx.xx.xx 1
(xx.xx.xx.xx = IP address for the localhost).

cheers,
pandian...

[alex]

You won't get a SIGSERV on routing problem.
You got errors during DB init - looks more like DB is screwed up . Either due to a HD failure or some "lethal" misconfiguration.
Try to restore last stable DB from daily backup.
By the way it is not the latest patch of 5.1.2.