![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||
Solution Type Technical Instruction Sure Solution 2195610.1 : Sl3000/SL8500 - How to Capture Logs for Debugging SLC Problems
In this Document
Applies to:StorageTek Library Console - Version 4.00 and laterSun StorageTek SL3000 Modular Library System - Version All Versions and later Sun StorageTek SL8500 Modular Library System - Version All Versions and later Information in this document applies to any platform. GoalHow to capture logs for debugging SLC problems. SolutionThree methods to gather logs for SLC issues: 1. For the Local Operator Panel, Oracle Linux Versions, at SLC_6.51 or greater and library code at SL3000_4.31 or SL8500_8.36 or greater collect the log via the SLC TransferFile menu and select “Operator Panel” in the log snapshot screen. 2. SLConsole logs are stored in a home directory folder on the remote machine SLC is executed on. Example: From a PC, the files are in a folder like this: slrussel->SLConsole->log, where slrussel is the user directory If running on Solaris, the files are in a hidden directory: ~slrussel/.SLConsole/log, where ~slrussel is the home directory The log directory will contain files similar to this: SLConsoleLog_1_0.txt Note; include all the files for the date when the error took place, along with the serial number of the library SLC was connected to when the problem occurred. 3. Remote SLC log capture for enhanced debugging: To enable debug in SLC, you need to do two things: FROM: FROM:
Attachments This solution has no attachment |
||||||||||||||
|