StorageTek ACSLS-Attached Automated Libraries: Common Problems and Error Messages

If errors exist in the configuration files for a StorageTek ACSLS-attached automated library, the system generates several error messages. These examples show common problems and the messages that the system generates.

StorageTek ACSLS Parameters File Errors

May 23 09:26:13 baggins stk-50[3854]: initialize: 
Syntax error in stk configuration file line 4. 
May 23 09:26:13 baggins stk-50[3854]: initialize: 
Syntax error in stk configuration file line 5.

Check your StorageTek parameters file for syntax errors. Ensure that each line begins with a keyword or a comment. For more information about the StorageTek parameters file, see stk(7) in Sun QFS and Sun Storage Archive Manager Reference Manual.

StorageTek ACSLS Library Errors

The following example shows drives that are frozen in the initializing state.

May 23 09:29:48 baggins stk-50[3854]: main: Waiting for 2 drive(s) to initialize
May 23 09:29:59 baggins stk-50[3854]: main: Waiting for 2 drive(s) to initialize
May 23 09:30:39 baggins stk-50[3854]: main: Waiting for 2 drive(s) to initialize
.
.
.
May 23 09:31:19 baggins stk-50[3854]: main: 2 drive(s) did not initialize.

The following example shows the samu utility's :r output.

ty eq status act use state vsn 
sg 51 ---------p 0 0% off drive set off due to ACS reported state 
sg 52 ---------p 0 0% off drive set off due to ACS reported state 
lt 61 ---------p 0 0% off drive set off due to ACS reported state 
tp 62 ---------- 0 0% off empty

A drive that is frozen in an initializing state or that does not initialize indicates a configuration error.

• Verify that the ACSLS software is running.

• Verify the host name.

• Use the ping command to determine whether you can you reach the host.

• Check the portnum specification in the StorageTek parameters file. In ACSLS 5.3, for example, the default port number, 50004, is used for a different application. Try a higher port number, such as 50014.

VSN Import Errors

This example shows messages that are generated after the samimport command was used to import a VSN to the library catalog, but the VSN was not in the StorageTek automated library. The cartridge must be present in the ACSLS-managed automated library before the samimport command can be successful.

May 20 15:09:33 baggins stk-50[6117]: view_media 
returned:STATUS_VOLUME_NOT_IN_LIBRARY 
May 20 15:09:33 baggins stk-50[6117]: add_to_cat_req: view_media: 
failed:STATUS_VOLUME_NOT_IN_LIBRARY. A

The sam-stkd daemon uses the ssi.sh script to ensure that a copy of the SSI daemon, ssi_so, is running. If ssi_so exits, the daemon starts another. If your site has its own version of ssi.sh, modify it to wait for a SIGTERM signal and then exit. The daemon sends a SIGTERM signal to stop the process. The /opt/SUNWsamfs/examples/ssi.sh file contains an example ssi.sh script. The system copies the ssi.sh script to /etc/opt/SUNWsamfs/scripts/ssi.sh during installation if one does not already exist.