Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2195610.1
Update Date:2017-11-14
Keywords:

Solution Type  Technical Instruction Sure

Solution  2195610.1 :   Sl3000/SL8500 - How to Capture Logs for Debugging SLC Problems  


Related Items
  • Sun StorageTek SL3000 Modular Library System
  •  
  • StorageTek Library Console
  •  
  • Sun StorageTek SL8500 Modular Library System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: Tape Library Control Software
  •  




In this Document
Goal
Solution


Applies to:

StorageTek Library Console - Version 4.00 and later
Sun 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.

Goal

 How to capture logs for debugging SLC problems.

Solution

Three 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:
1 - pass in the parameters to the SLC to increase its debug level
2 - define path to file(s) that will capture standard err and standard out. To do this, in the installation directory of SLC(default : C:\Program Files\Sun\StorageTekLibraryConsole), find the SLConsole.lax file and open it in a text editor. Modify the following lines :
FROM:
lax.command.line.args=$CMD_LINE_ARGUMENTS$
TO:
lax.command.line.args=$CMD_LINE_ARGUMENTS$ -c -e 7

FROM:
lax.stderr.redirect=
TO:
lax.stderr.redirect=C:\\slc.err
(or where you want the error log file to go. be sure to use '\\' to separate path)

FROM:
lax.stdout.redirect=
TO:
lax.stdout.redirect=C:\\slc.out
(or where you want the log file to go. be sure to use '\\' to separate path)

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback