ADSM-L

ADSM-server cored

1996-12-30 07:29:06
Subject: ADSM-server cored
From: Henk ten Have <hthta AT SARA DOT NL>
Date: Mon, 30 Dec 1996 13:29:06 +0100
Hi all,

after running fine for month, the ADSM-server cored.

-The activity log ends with:
12/26/96   19:30:12      ANR0400I Session 17771 started for node HORUS_C (AIX).
12/26/96   19:30:12      ANR0400I Session 17771 started for node HORUS_C (AIX).
12/26/96   19:30:48      ANR8337I 3590 volume 000535 mounted in drive 3590-3
                          (/dev/rmt3).
12/26/96   19:31:24      ANR0811I Inventory client file expiration started as
                          process 993.
12/26/96   19:31:48      ANR0400I Session 17772 started for node ISIS-S315 
(AIX).
12/26/96   19:31:48      ANR1440I All drives in use.  Process 992 being 
preempted
                          by higher priority operation.
12/26/96   19:31:48      ANR1213I Backup process 992 terminated for storage pool
                          3494POOL - process canceled.
12/26/96   19:31:48      ANR1214I Backup of primary storage pool 3494POOL to 
copy
                          storage pool 3494POOL.CP has ended.  Files Backed Up: 
0,
                          Bytes Backed Up: 0, Unreadable Files: 0, Unreadable
                          Bytes: 0.

-In the corefile I found the following messages ("strings core"):
ANR1440I All drives in use.  Process %d being preempted by higher priority 
operation.~
ANR1440I All drives in use.  Process %d being preempted by higher priority 
operation.~
ANR7850I Process 45136 has terminated on signal 11 (Segmentation Violation).

-And with dbx ("dbx dsmserv core"):
IOT/Abort trap in raise at 0xd0078900
IOT/Abort trap in raise at 0xd0078900
0xd0078900 (raise+0x20) 80410014          l   r2,0x14(r1)
(dbx) where
raise(??) at 0xd0078900
abort() at 0xd0019a14
SignalTrap(??, ??, ??) at 0x10006638
asCancelInputMountWait(??, ??) at 0x100d3eb8
bfCancelMediaWaits(??, ??) at 0x10109440
AfCopyCancel(??, ??, ??) at 0x10119638
procCancelProcess(??, ??) at 0x100210f8

So, to me it has something to do with all drives in use and a process is
being preempted by higher priority operation (in this case HSM-activity
from node ISIS-S315).

Anyone seen this before and/or any suggestions?

(running ADSM V2.1.0.9 on a SP2 (AIX 4.1.4.0) using 3494 with 4 3590 units,
 backup/archive client's 2.1.0.5 on AIX 3.2, AIX 4.1.4, SunOs, Solaris, SGI,
 HSM client 2.1.0.5 on AIX 4.1.4.0)

Regards,

Henk ten Have                   SARA, Academic Computing Services Amsterdam
Systems Programmer              Kruislaan 415
E-mail: hthta AT sara DOT nl           1098 SJ Amsterdam
Phone : +31205923000            The Netherlands
<Prev in Thread] Current Thread [Next in Thread>
  • ADSM-server cored, Henk ten Have <=