Conference mayday::acb

709.0. "error setting delay: invalid argument" by KERNEL::GRIFFITHSJ () Fri May 23 1997 15:54

    Hello 
    
    This may be obivous but I know nothing about ACB. Customer rebooted
    system and since then has had the following problem:-
    
    
    The ACB$SYMBIONT.LOG constantly logs error setting delay: invalid
    argument. He says ACB is working at least on the TTA2: port.
    The log file gets very large very quickly.
    
    The system is Vax running V6.2
    
    ACB is version V2.2-001
    
    ACB$symbiont.log example :-
    
    $ set noverify
    %PURGE-W-SEARCHFAIL, error searching for
    SYS$COMMON:[SYSMGR]ACB$START_DECNET.LOG
    ;*
    -RMS-E-FNF, file not found
    %ACB-I-ALLFINE, no accounting record recovered
    001: ** 23-MAY-1997 10:30:30.53 ** LIB$SPAWN flags to be used are 109
    001: ** 23-MAY-1997 10:30:30.54 ** opening ACB authorization database
    001: ** 23-MAY-1997 10:30:30.74 ** Error converting inactivity time,
    Delta time
    required, absolute time supplied
    001: ** 23-MAY-1997 10:30:30.77 ** setting the thread scheduling policy
    001: ** 23-MAY-1997 10:30:30.82 ** creating thread Accounting Mailbox
    Processing
    001: ** 23-MAY-1997 10:30:30.82 ** thread Accounting Mailbox Processing
    has been
     created
    001: ** 23-MAY-1997 10:30:30.82 ** creating thread Service Mailbox
    Processing
    001: ** 23-MAY-1997 10:30:30.83 ** thread Service Mailbox Processing
    has been cr
    eated
    001: ** 23-MAY-1997 10:30:30.83 ** creating thread Old (V2.0) Service
    Mailbox Pr
    ocessing
    001: ** 23-MAY-1997 10:30:30.83 ** thread Old (V2.0) Service Mailbox
    Processing
    has been created
    001: ** 23-MAY-1997 10:30:30.87 ** checking if line LTA20:, defined for
    node HAZ
    VX9 is allowed on node HAZVX9
    001: ** 23-MAY-1997 10:30:30.91 ** creating thread TTY service port
    001: ** 23-MAY-1997 10:30:30.91 ** thread TTY service port has been
    created
    001: ** 23-MAY-1997 10:30:30.91 ** checking if line TTA2:, defined for
    node HAZV
    X9 is allowed on node HAZVX9
    001: ** 23-MAY-1997 10:30:30.91 ** creating thread TTY service port
    001: ** 23-MAY-1997 10:30:30.91 ** thread TTY service port has been
    created
    001: ** 23-MAY-1997 10:30:30.98 ** creating thread Accounting TS update
    001: ** 23-MAY-1997 10:30:30.98 ** thread Accounting TS update has been
    created
    001: ** 23-MAY-1997 10:30:30.98 ** creating thread Inactivity scan
    001: ** 23-MAY-1997 10:30:30.98 ** thread Inactivity scan has been
    created
    001: ** 23-MAY-1997 10:30:30.98 ** waiting on shutdown condition
    003: ** 23-MAY-1997 10:30:30.98 ** ready to process message on
    accounting mailbo
    x
    004: ** 23-MAY-1997 10:30:31.02 ** ready to process message on service
    mailbox
    008: ** 23-MAY-1997 10:30:31.02 ** time-stamp delay is 10 sec, 0 nsec
    error setting TS delay: invalid argument
    005: ** 23-MAY-1997 10:30:31.14 ** ready to process message on old
    (V2.0) servic
    e mailbox
    006: ** 23-MAY-1997 10:30:31.14 ** working with line LTA20:
    006: ** 23-MAY-1997 10:30:31.14 ** proceed to initialization of line
    LTA20:
    error setting LAT connection delay: invalid argument
    006: ** 23-MAY-1997 10:30:31.14 ** LAT-connecting to line LTA20: (retry
    left: 1)
    007: ** 23-MAY-1997 10:30:31.34 ** working with line TTA2:
    007: ** 23-MAY-1997 10:30:31.34 ** proceed to initialization of line
    TTA2:
    007: ** 23-MAY-1997 10:30:31.34 ** sending the init sequence on line
    TTA2:
    error setting TS delay: invalid argument
    error setting TS delay: invalid argument
    error setting TS delay: invalid argument
    error setting TS delay: invalid argument
    error setting TS delay: invalid argument
    006: ** 23-MAY-1997 10:30:31.54 ** LAT connection done on line LTA20:
    006: ** 23-MAY-1997 10:30:31.58 ** sending the init sequence on line
    LTA20:
    error setting delay: invalid argument
    006: ** 23-MAY-1997 10:30:31.58 ** ready to login user on line LTA20:
    error setting delay: invalid argument
    007: ** 23-MAY-1997 10:30:31.58 ** ready to login user on line TTA2:
    007: ** 23-MAY-1997 10:30:31.58 ** read done on TTA2:, status 1
    007: ** 23-MAY-1997 10:30:31.58 ** read from line TTA2:
    007: ** 23-MAY-1997 10:30:31.58 ** read done on TTA2:, status 1
    007: ** 23-MAY-1997 10:30:31.60 ** read from line TTA2: <LF>OK
    007: ** 23-MAY-1997 10:30:31.60 ** modem on line TTA2: has been
    correctly inited
    error setting TS delay: invalid argument
    error setting TS delay: invalid argument
    error setting TS delay: invalid argument
    error setting TS delay: invalid argument
    
    
    
    
    
    Thanks Jim

        Well, ACB appears to use CMA (judged from the fact that ACB$
        images area linked against CMA$ stuff). Now CMA aka threads was
        one of the major components affected by the delta time issue,
        i.e. 19-may-1997 more than 9999 days has passed since
        1-jan-1970 (origin of Unix time...).
        
        Did the customer implement Delta time patch aka VAXLIBR06_070 or
        ALPLIBR05_070 prior 19-may-1997?
             
        
        _veli