HP Storage Essentials V5.1 Installation Guide Second Edition (Linux Release) (T4283-96055, November 2006)

Storage Essentials 5.1 Installation Guide 305
17 Troubleshooting
This chapter describes the following:
• ”“Data is late or an error occurred” Message” on page 305
• ”appiq.log Filled with Connection Exceptions” on page 305
• ”Receiving “HTTP ERROR: 503" When Accessing the Management Server” on page 306
• ”Permanently Changing the Port a CIM Extension Uses (UNIX Only)” on page 308
• ”Configuring UNIX CIM Extensions to Run Behind Firewalls” on page 309
• ”Volume Names from Ambiguous Automounts Are Not Displayed” on page 313
• ”Installing the Software Security Certificate” on page 313
• ”Troubleshooting After Upgrading” on page 316
• ”Troubleshooting Discovery and Discovery Data Collection/Get Details” on page 317
• ”Troubleshooting Topology Issues” on page 323
• ”Troubleshooting Provisioning” on page 334
• ”Troubleshooting Hardware” on page 335
“Data is late or an error occurred”
Message
If you see the message “Data is late or an error occurred” when you try to obtain information from
a UNIX host, verify you were logged in as root when you started the CIM Extension (./start). You
must be logged in as root if you want to use the ./start command, even if you are using the
./start -users username command, where username is a valid UNIX account.
The CIM Extension only provides the information within the privileges of the user account that
started the CIM Extension. This is why you must use root to start the CIM Extension. Only root has
enough privileges to provide the information the management server needs.
If you continue to see the message, contact customer support.
appiq.log Filled with Connection
Exceptions
When an Oracle REDO log becomes corrupt, the management server is unable to connect to the
database. Whenever the management server is unable to connect to the Oracle database, it writes
to the appiq.log file. Many exceptions may cause the Application Log on Windows to become full.
To fix the problem, stop the management server and Oracle. Then, remove the corrupted REDO log,
as described in the following steps:
1. Stop the AppStorManager service, which is the service the management server uses.