My Oracle Support Banner

The "acsss enable" command fails with with message "Method or service exit timed out. Killing contract" (Doc ID 2696384.1)

Last updated on AUGUST 14, 2020

Applies to:

Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) - Version 8.4 and later
Information in this document applies to any platform.
The ACSLS server was rebooted, but ACSLS would not initialize.
Attempts to issue the ACSLS "acsss enable" command failed attempting to start the acsls service.
Attempts to start ACSLS starting all of the individual services separately in the correct order also failed when attempting to start the acsls service.

Symptoms

The ACSLS acsls service does not complete initialization. 
The acsss_event.log displays messages like the following:

2020-07-30 16:40:09 storage server[0]:
347 N ss_main.c 4  564
-----------------------------------------------------------------
ss_main: Initiation started, Oracle ACSLS (Automated Cartridge System Library 
Software) 8.4.0

2020-07-30 16:40:46 ACSSA[0]:
1439 N sa_demux.c 1  296
Server system recovery started.

2020-07-30 16:40:47 ACSSA[0]:
1434 N sa_demux.c 1  296
ACS   0: Online.

2020-07-30 16:40:47 ACSLM[0]:
37 N lm_msg_hdlr.c 1  1079
lm_msg_hdlr: LMU READY received for ACS Identifier   0

2020-07-30 16:40:48 CSI[0]:
935 N csi_mt_init.c 1 147
ONC RPC: csi_mt_init(): Initiation Started

2020-07-30 16:40:48 CSI[0]:
964 N csi_rpcuinit.c 1  236
ONC RPC: csi_rpcuinit(): Unmapped previously registered RPC service.
....................................................................(more messages like above)
2020-07-30 16:40:48 CSI[0]:
938 N csi_mt_init.c 1 267
ONC RPC: csi_mt_init(): Initiation Completed

2020-07-30 16:40:51 storage server[0]:
351 N ss_main.c 4  810
ss_main: Initiation completed

2020-07-30 16:40:52 ACSLH[0]:
2551 I Co_status.C 2  1383
Checking for LSM 0,0 status ...

2020-07-30 16:40:57 ACSLH[0]:
2552 I Co_status.C 2  3106
LSM 0,0 status  Ready, on-line,door closed.
   hand-0 operative, empty.
     hand-1 operative, empty.  
...................................................................(more messages like above)
2020-07-30 16:41:18 ACSSA[0]:
1436 N sa_demux.c 1  296
Server system recovery complete.

2020-07-30 16:41:18 ACSSA[0]:
1418 N sa_demux.c 1  296
Server system idle.

2020-07-30 16:48:08 storage server[0]:
356 N ss_main.c 4  1129
ss_main: Termination invoked, STATUS_TERMINATED

2020-07-30 16:48:08 ACSSA[0]:
1458 N sa_demux.c 1  296
Server system terminated.

2020-07-30 16:48:08 CSI[0]:
969 N csi_mt_shutdown.c 1 141
ONC RPC: csi_mt_shutdown(): Termination Started

2020-07-30 16:48:08 CSI[0]:
970 N csi_mt_shutdown.c 1 188
ONC RPC: csi_mt_

With no message to indicate why termination was invoked. 


The acsls_start.log shows the following (this example is from a Solaris host):

[ Jul 30 16:40:01 Enabled. ]
[ Jul 30 16:40:01 Executing start method ("/lib/svc/method/svc-acsls start"). ]
/export/home/ACSSS/bin/acsls.startup: Initializing ACSLS.
[ Jul 30 16:56:15 Method or service exit timed out.  Killing contract 1035. ]
[ Jul 30 16:56:15 Method "start" failed due to signal KILL. ]
[ Jul 30 16:56:15 Executing start method ("/lib/svc/method/svc-acsls start"). ]
[ Jul 30 16:56:16 Method "start" exited with status 0. ]
[ Jul 30 16:56:16 Stopping because all processes in service exited. ]
[ Jul 30 16:56:16 Executing stop method ("/lib/svc/method/svc-acsls stop"). ]
[ Jul 30 16:56:18 Method "stop" exited with status 0. ]
[ Jul 30 16:56:18 Restarting too quickly, changing state to maintenance. ]
[ Jul 30 17:04:29 Leaving maintenance because disable requested. ]
[ Jul 30 17:04:29 Disabled. ]

With the message "Method or service exit time out" indicating the failure.

The SL8500 library hbc/log/stk/warning.log would show errors such as:

2020-07-30T16:56:15.176, 1.0.0.0.0, root, default, internal, 0, warn, 3912, "Hli connection status change - transition to non-operational", port=10876807/skt/50001/xx.xx.xx.xx

A message that indicates a possible network issue.  However, the acsls.log  shows no LMU problems.

Changes

 The ACSLS server was rebooted. 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.