Storage Resource Manager Enterprise Edition Installation Guide

C–20 Storage Resource Manager Enterprise Edition
SRM Troubleshooting Guide
If SRM does not open the pipe in this amount of time, OEMSCANIO will read the
agent’s data, and write it to a new temporary file (by default with the
FILE_FLAG_DELETE_ON_CLOSE attribute set). It will then create a new
OEMSCANIO process which is set to read this file, and will continue to wait for SRM
to pick up the scan posting. Once the data is written to the file and the new process is
started, the CGI process will terminate. Since the data being posted by the UNIX
agent is also read, it will also terminate about the same time.
The new process will wait up to 30 minutes for SRM to open the pipe. When SRM
opens the pipe, it will copy the contents of the file into the pipe. In any case, it will
close the file when it terminates.
There are 2 registry keys that can be used in debugging problems:
• HKEY_LOCAL_MACHINE\SOFTWARE\Storeway\OEMScan\ScanTimeout
(default 120): The amount of time OEMSCANIO waits before writing scan data
to a file and starting a new process. If set to 0, scan data is always written to a file.
• HKEY_LOCAL_MACHINE\SOFTWARE\Storeway\OEMScan\RetainBufFile
(default 0): Determines if the FILE_FLAG_DELETE_ON_CLOSE attribute is set
on the created file. If set to 1, the attribute is not set, and files are not deleted. They
can then be used to see what data was posted. Note that files will have to be
deleted manually.
Standard NT Mechanisms for Debugging SRM
Problems
The following tools are used for debugging SRM problems:
Event Log and IIS Log
A key troubleshooting aid is monitoring the NT Event Log. SRM writes events to the
“application log” on the SRM Server machine.
By default, only more serious events are logged.
For UNIX components, additional logging can be enabled by creating the following
registry key (if it does not already exist) and setting it to 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Storeway\OEMScan\Log
NOTE: When viewing an event log on a different system, you must have the same version of
SRM installed on the machine you intend on viewing the event log on. If not, the errors listed in
the event log will have incomplete entries.