>Hi *SM-ers!
>My TSM 3.7.3.0 server is crashing at least once a day for the last 5 days.
>There no addition information in the Activity log. The only output is a core
>dump and some unclear messages in the dsmserv.err:
>
>09/21/2000 10:14:28 ANR7834S Thread 49 (tid 3196) terminating on signal 11
>(Segmentation violation).
>09/21/2000 10:14:28 ANR7834S GPR 0: 0x00000000, 1: 0x366c7c80, 2:
>0x3012003c, 3: 0x00000000
>09/21/2000 10:14:28 ANR7834S GPR 4: 0x31a30fec, 5: 0x13711301, 6:
>0x11020000, 7: 0x00000000
>09/21/2000 10:14:28 ANR7834S GPR 8: 0x1000732b, 9: 0x1000732b, 10:
>0x00000000, 11: 0x000034e0
>09/21/2000 10:14:28 ANR7834S GPR 12: 0x00000200, 13: 0x366cbf9c, 14:
>0x35b2edf0, 15: 0x00000000
>09/21/2000 10:14:28 ANR7834S GPR 16: 0x0000018c, 17: 0x366cbc6c, 18:
>0x366c9600, 19: 0x366c89c4
>09/21/2000 10:14:28 ANR7834S GPR 20: 0x00000002, 21: 0xffffffff, 22:
>0x35fd4038, 23: 0x00041e19
>09/21/2000 10:14:28 ANR7834S GPR 24: 0x35fd4020, 25: 0x35b205f0, 26:
>0x00000000, 27: 0x00000001
>09/21/2000 10:14:28 ANR7834S GPR 28: 0x0000079e, 29: 0x366c8dc4, 30:
>0x366c80f8, 31: 0x35fd4000
>09/21/2000 10:14:28 ANR7834S IAR: 0x100121fc LR: 0x10081d98 CONTEXT:
>0x366c7900
If you have dbx installed then from the server directory rename the core dump
to something like core.dump then bring up dbx with
dbx ./dsmserv core.dump
Then under dbx use the command where to get a callback trace from the
stack. This should be enough to know if this is a known problem. If
not then call support so we can look at the core dump. If you need to
go that route then they will need the core file, your dsmserv executable
and the dsmserv.err file.
David Bohm
TSM server development
email - dbohm AT tivoli DOT com
|
