Recovering From An Scm Error; Recovering From An Httpd Service Error - IBM Storwize V7000 Unified Problem Determination Manual

Table of Contents

Advertisement

Procedure
1. Log in as root.
2. Issue the service nfsd start command.
3. If the problem persists, restart the node.
4. If the restart action does not resolve the issue, contact the next level of support.

Recovering from an SCM error

Use this procedure to recover from a service configuration management (SCM)
error.
About this task
Complete the following procedure if output from the lshealth -r CLI command
contains a line similar to the following:
SCM
Note: This procedure involves analyzing various logs depending on the errors
displayed by the initial SCM error log.
Procedure
1.
2. To know the error code, run the lslog command or open the graphical user
3. Compare the results returned by lslog command with lshealth -i SCM
4. Open the CNSCM log located at /var/log/cnlog/cnscm for the file module that
5. Review the error entries around the listed time stamp and then check the log
6. Review the log entries and try to match the entries with the lslog output. If
7. Based on the log entries, check the appropriate corresponding log. If the issue
8. If the log entries do not help resolve the error, contact the next level of support.

Recovering from an httpd service error

Use this procedure to recover from an httpd service error when the service is
reported as unhealthy or off.
About this task
Procedure
To fix the httpd error, perform the following steps:
1. Attempt to start the http service manually.
280
Storwize V7000 Unified: Problem Determination Guide Version
ERROR SCM system has found some errors
If an error is displayed, run the lshealth -i SCM command to show the details
of the component with the error. SCM is a component, that monitors other
components. Ensure to note the details shown by the Message and Value
columns.
interface (GUI) Eventlog page.
command. This procedure helps you in mapping the error. If you are not able
to link the lshealth -i SCM output with the lslog output, continue to the next
step.
reported the error.
for issues that seem related that occurred before the listed time stamp. For
example, you might find GPFS-related issues appearing earlier and later, too.
you are not able to match the entries, continue to the next step.
appeared to be related to GPFS, for example, you could look for the root cause
in /var/adm/ras/mmfs.log.

Advertisement

Table of Contents
loading

Table of Contents