Storage Resource Manager Enterprise Edition Installation Guide

C–28 Storage Resource Manager Enterprise Edition
SRM Troubleshooting Guide
If gdb (the gnu debugger) is present on the agent system, it is also possible to attach to
the “hung” process. If the stack shows the following profile, the above described
situation is occurring:
#0 0xff1955fc in _read ()
#1 0x50028 in URLReadResult (sid=4, buf=0xffbef640 “”, len=1024) at urlio.c:425
#2 0x48fb4 in SendOutput (s=0xd2698) at srmagent.cpp:806
#3 0x47284 in main (argc=1, argv=0xffbefe04) at srmagent.cpp:454
Does SRM Support AFS or DFS?
UNIX agents does not report local access to these network file systems. Note that
these file systems are complex virtual entities, with various levels of caching and
replication. However, they ultimately resolve to local, conventional file systems on
various servers (e.g. UFS, VxFS, AIX, JFS) which can be scanned and will be mapped
to physical disks.
OEM Event Log Messages
This section describes event log messages that are created by the SRM UNIX
components.
OEMScanner Messages
The following are OEMScanner messages:
Messages always logged (don’t require registry key settings)
• MessageId=11 SymbolicName=OEMSCAN_SCAN_IN_PROGRESS
SRM attempted to start a scan while a scan is already in progress. Only one scan
per object instance is supported.
Internal SRM error. The start method of the COM object was called multiple
times.
• MessageId=16 SymbolicName=OEMSCAN_UNSUPPORTED_SCAN
The scan requested is unsupported: worker type <integer scan type>.
Internal SRM error. The get_Supported method was called with a value other than
0=Computer, 1=File, or 2=OneDown
• MessageId=17 SymbolicName=OEMSCAN_GETHOST_ERR