ACSLS - re_vary_lsm: Vary failed, message STATUS_NOT READY (Doc ID 1360720.1)

Last updated on MAY 12, 2016

Applies to:

Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) - Version 8.0 to 8.4 [Release 8.0]
Information in this document applies to any platform.
***Checked for relevance on 24-Apr-2013***
***Checked for relevance on 12-May-2016***

Symptoms

1.  ACSLS won't come up.  acsss enable shows ACSLS in maintenance mode.

2.  The acsss_event.log shows VARY LSM errors:
     
     2011-09-15 17:23:39 VARY[2]:
     2563 E va_lsm_stat.c 1 3569
     va_lsm_state:st_ptp_status: LSM 0, 3 type changed from 8500 to 8509; LSM
     remains offline.

    2011-09-15 17:23:39 VARY[2]:
    2564 I va_lsm_stat.c 1 3572
    va_lsm_state:st_ptp_status: Please update your ACSLS library configuration
    using Dynamic config or acsss_config.
    ....

    2011-09-15 17:23:40 VARY[2]:
    2563 E va_lsm_stat.c 1 3569
    va_lsm_state:st_ptp_status: LSM 0, 2 type changed from 8500 to 8509; LSM
    remains offline.
    ...
    2011-09-15 17:23:42 VARY[2]:
    2563 E va_lsm_stat.c 1 3569
    va_lsm_state:st_ptp_status: LSM 0, 0 type changed from 8500 to 8509; LSM
    remains offline.
    ...
    2011-09-15 17:23:42 RECOVERY[0]:
    91 N re_vary_lsm.c 2 285
    re_vary_lsm: Vary failed, message status STATUS_NOT_READY

    2011-09-15 17:23:42 ACSSA[0]:
    1437 N sa_demux.c 1 296
    Server system recovery failed.

    2011-09-15 17:23:43 ACSLM[0]:
    922 N lm_wait_proc.c 1 301
    lm_wait_proc: STATUS_PROCESS_FAILURE received from RECOVERY -PID(5497)

    2011-09-15 17:23:43 ACSLM[0]:
    32 N lm_wait_proc.c 1 307
    lm_wait_proc: Unexpected error STATUS_PROCESS_FAILURE, exiting to ACSSS

    2011-09-15 17:23:43 storage server[0]:
    354 N ss_main.c 4 871
    ss_main: exit status (76), STATUS_RECOVERY_FAILED, received from acslm

    2011-09-15 17:23:43 storage server[0]:
    356 N ss_main.c 4 1145
    ss_main: Termination invoked, STATUS_RECOVERY_FAILED

Changes

The ACSLS server and the tape libraries were shutdown prior to a datacenter maintenance activity. Or,
the library configuration may have changed - like when applying new capacity hardware license code.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms