Conference noted::latmaster

1314.0. "LATACP in strange COM-state..." by BACHUS::VANLOOCK (Patrick DTN 856-8648) Tue Jun 03 1997 11:00

Hi,

Got strange problem with LATACP reported by a customer:
(Alpha VMS 6.2 1H3)

Process LATACP becomes in status COM although no resources are
actually being taken, 
dcl-command:  sh proc/id=pid-of-latacp/...  'hangs'
LATCP-commands hang too...
Monitor system shows cpu only 20% used, memory and diskresources
seems to be ok...

As a result: users can't get connected any longer via lat to this system;
trying to (re-)start LAT-queues give only an 'abort'-message.

Customer got this problem on two different Alpha's, sometimes
at about the same time (they are offering a 'common' LAT-service).

Rebooting system cures only for a while: sometimes, the problem is
back afer 2 hours...

SDA-info about latacp: STATE: COM, Process Status: WAKEPEN !!
trying to get more info returns message like "process is swapped out"
   
   Process index: 0020   Name: LATACP   Extended PID: 20E00420
   -----------------------------------------------------------
   Process status:        00959001  RES,WAKEPEN,NOACNT,PHDRES,LOGIN,NODELET
   Required capabilities: 0000000C  QUORUM,RUN
   
   PCB address              814E5540    JIB address              81485CC0
   PHD address              8B904000    Swapfile disk address    00000000
   Master internal PID      00010020    Subprocess count                0
   Internal PID             00010020    Creator internal PID     00000000
   Extended PID             20E00420    Creator extended PID     00000000
   State                       COM      Termination mailbox          0000
   Previous CPU Id          00000000    Current CPU Id           00000000
   Previous ASNSEQ  0000000000000489    Previous ASN     000000000000002B
   Current priority               15    # of threads     0000000000000000
   Initial process priority       12    Delete pending count         0
   Base priority                  12    AST's active                 NONE
   UIC                [00001,000004]    AST's remaining               100
   Mutex count                     0    Buffered I/O count/limit    32767/32767
   Waiting EF cluster              0    Direct I/O count/limit      32767/32767
   Abs time of last event   0071F7D7    BUFIO byte count/limit     261696/261696
   Event flag wait mask     0000000D    # open files allowed left     126
   Swapped copy of LEFC0    00000000    Timer entries allowed left     16
   Swapped copy of LEFC1    00000000    Active page table count         0
   Global cluster 2 pointer 00000000    Process WS page count          46
   Global cluster 3 pointer 00000000    Global WS page count            0
   
ana/imag/inter SYS$COMMON:[SYSEXE]LATACP.EXE;1
      Image Identification Information

                image name: "LATACP"
                image file identification: "V2.0-181A"
                image file build identification: "X61Q-SSB-0000"
                link date/time:  4-MAY-1995 22:52:19.10
                linker identification: "A11-12"

ana/imag/inter SYS$COMMON:[SYSEXE]LATCP.EXE;1
       Image Identification Information

                image name: "LATCP"
                image file identification: "V2.0-040"
                image file build identification: "X61Q-SSB-0000"
                link date/time:  4-MAY-1995 22:55:26.03
                linker identification: "A11-12"

ana/imag/inter SYS$COMMON:[SYSEXE]LATSYM.EXE;1
       Image Identification Information

                image name: "LATSYM"
                image file identification: "V6.0-040"
                image file build identification: "X61Q-SSB-0000"
                link date/time:  4-MAY-1995 22:55:46.63
                linker identification: "A11-12"

ana/ima/inter SYS$COMMON:[SYS$LDR]SYS$LTDRIVER.EXE;2
       Image Identification Information

                image name: "SYS$LTDRIVER"
                image file identification: "X-3"
                image file build identification: "X61Q-SSB-IF00"
                link date/time: 26-APR-1996 12:44:07.62
                linker identification: "A11-12"

Any idea about what is going wrong there???

Regards,

Patrick
                 

    Sounds like you'll need to escalate this.. How about some PC samples?
    What are the Alpha platform models showing the problem? (SMP?)
    Have you applied the 'AST delivery out of order' fix ECO?
    
    John.

    John,
    
    Thanks for reply: I'll have a look about that fix-kit
    But in meantime, we think that this problem might be related
    with a customer-written DCL-com-procedure that checks CPU-
    consumption of interactive processes This proc. tries to locate
    'looping' processes and kill those... 
    This proc. was started for first time last Friday... and after 
    customer stopped this proc.  LATACP was behaving well...
    Customer will keep it like that one more week ... 
    
    Regards,
    
    Patrick