Hello.
I have a problem with TSM server 5.1.6.5 core dumping during heavy load on
AIX 4.3.3


dsmserv.err says:


06/06/2003 03:26:30  ANR7834S Thread 127 (tid 7ff7) terminating on signal 11 
(Segmentation violation).
06/06/2003 03:26:30  ANR7834S GPR  0: 0x00000000,   1: 0x7e1f15e0,   2: 
0x3025f2a4,   3: 0x30248a64
06/06/2003 03:26:30  ANR7834S GPR  4: 0x000013b4,   5: 0xffffffff,   6: 
0x41564f4c,   7: 0x7cc1e838
06/06/2003 03:26:30  ANR7834S GPR  8: 0x00000000,   9: 0x302482b0,  10: 
0x00000000,  11: 0x05593d30
06/06/2003 03:26:30  ANR7834S GPR 12: 0x101a7770,  13: 0xec2e19dc,  14: 
0x2851407e,  15: 0xb79c809c
06/06/2003 03:26:30  ANR7834S GPR 16: 0x1f62beeb,  17: 0x474a4637,  18: 
0xbed4e5ad,  19: 0x7521bb37
06/06/2003 03:26:30  ANR7834S GPR 20: 0x17f6e454,  21: 0x4afbee52,  22: 
0xf54bd335,  23: 0x3af69151
06/06/2003 03:26:30  ANR7834S GPR 24: 0x8d9a2999,  25: 0x23d1ef76,  26: 
0x00000002,  27: 0x302482b0
06/06/2003 03:26:30  ANR7834S GPR 28: 0x3003b1b0,  29: 0x00000000,  30: 
0x3003b1b0,  31: 0x7cb64578
06/06/2003 03:26:30  ANR7834S IAR: 0x101a8e00   LR: 0x101a77fc   CONTEXT: 
0x7e1f1260
06/06/2003 03:26:30  ANR7833S Server thread 1 terminated in response to program 
abort.
... and so on other threads.



Also there is an information in AIX's error log:



LABEL:          CORE_DUMP
IDENTIFIER:     C60BB505

Date/Time:       Fri Jun  6 03:30:19 
Sequence Number: 64369
Machine Id:      0053714A4C00
Node Id:         scb
Class:           S
Type:            PERM
Resource Name:   SYSPROC

Description
SOFTWARE PROGRAM ABNORMALLY TERMINATED

Probable Causes
SOFTWARE PROGRAM

User Causes
USER GENERATED SIGNAL

        Recommended Actions
        CORRECT THEN RETRY

Failure Causes
SOFTWARE PROGRAM

        Recommended Actions
        RERUN THE APPLICATION PROGRAM
        IF PROBLEM PERSISTS THEN DO THE FOLLOWING
        CONTACT APPROPRIATE SERVICE REPRESENTATIVE

Detail Data
SIGNAL NUMBER
           6
USER'S PROCESS ID:
       72888
FILE SYSTEM SERIAL NUMBER
           6
INODE NUMBER
       67595
PROGRAM NAME
dsmserv
ADDITIONAL INFORMATION
pthread_k 80
??
_p_raise 64
raise 34
abort B8
AbortServ 80
TrapHandl 13C
??
??

Symptom Data
REPORTABLE
1
INTERNAL ERROR
0
SYMPTOM CODE
PCSS/SPI2 FLDS/dsmserv SIG/6 FLDS/AbortServ VALU/80



There is also a core file (which I can put on some http/ftp to trace).

This happens every 2-3 days. I don't know the exact load of TSM server then
(I don't know yet if the storage pools are enough and so on), but during
this one hour (03:00-04:00 am) there are aprox. 100 mounts on 3494 library (8
drives) and around 100 concurent client sessions accessing server (mostly
incremental backup).

Anyone has idea what can cause it?


-- 
Przemysław Maciuszko
Agora SA