ACSLS - Not Getting Any Mount Request From the SMC Application
(Doc ID 2813348.1)
Last updated on JULY 11, 2022
Applies to:
Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) - Version 8.5.1 to 8.5.1 [Release 8.0]StorageTek SL4000 Modular Library System - Version All Versions and later
Information in this document applies to any platform.
Symptoms
ACSLS had to be restarted due to a library maintenance activity. After fixing the library problem, ACSLS failed to restart because of a defunct acslm process.
ACSLS did restart successfully after terminating the defunct process. However, ACSLS appears to be not communicating with the mainframe (SMC) application.
The xapi_startup.log file shows an invalid command, "XXSE":
Attempting startup of /export/home/ACSSS/bin/xapi_server...
(04693) 1006 12:00:16 SMC9000 Copyright (c) 2012, 2016, Oracle and/or its affiliates. All rights reserved.
(04693) 1006 12:00:16 SMC9001 Communication server initialization starting
(04693) 1006 12:00:16 SMC9028 Startup parameter EXCL successfully processed
(04693) 1006 12:00:16 SMC9028 Startup parameter RESET successfully processed
(04693) 1006 12:00:17 SMC9054 Startup file=/export/home/ACSSS/log/xapi/xapi_startup_file processing starting
(04693) 1006 12:00:17 SMC9024 XXSE is an invalid command <<<<---------
(04693) 1006 12:00:17 SMC9055 Startup file=/export/home/ACSSS/log/xapi/xapi_startup_file processing complete; RC=8
(04693) 1006 12:00:17 SMC9002 Communication server initialization complete
(04693) 1006 12:00:17 SMC9003 Communication server release=8.5.1 active on host=DC2-ACSLS, port=50020, TapePlex=C2-ACSLS
The SMC log is showing this error:
--
SMC0260 TAPEPLEX C2-ACSLS commpath ACSLS2 inactive; RC=72, login error=XUDB not defined
Changes
ACSLS had to be restarted after a library problem.
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 |