Troubleshooting

This chapter covers the following topics:

• How to view log data

• How to read WBEM error messages

• List of error messages

Viewing Log Data Through Log Viewer

The WBEM logging service enables application developers and writers of providers to write log messages to the log files. WBEM log files to track errors, warnings, and informational messages that the management subsystem generates. For example, you might want to write out log messages under the following conditions:

• When a system is not able to access a serial port

• When a system successfully mounts a file system

• When the number of processes that are running on a system exceeds the allowed number

After you have created a log record, you can start the Solaris Management Console application and Log Viewer. A log record is automatically created when you start the Solaris Management Console software.

You can view all details of a log record in the Solaris Management Console Log Viewer.

How to Start the Solaris Management Console Application and Log Viewer

1. To start the Solaris Management Console, type this command:

   $ smc

   
   

2. In the Navigation panel, either double-click This Computer or click the expand/compress icon next to This Computer.

   A tree of commands is displayed below This Computer.

3. Double-click System Status.

   The Log Viewer icon is displayed.

4. Click the Log Viewer icon.

   Log Viewer starts.

Figure 9-1 Solaris Management Console Application With Log Viewer Selected

About WBEM Error Messages

The CIM Object Manager (CIMOM) generates error messages that are used by both the Managed Object Format (MOF) compiler and CIM Workshop. The MOF compiler appends a line to the error message that indicates the line number in which the error occurs in the .mof file.

Note - For more information on the MOF compiler, see the mofcomp(1M) man page.

Parts of an Error Message

An error message consists of the following parts:

• Unique identifier - A character string that identifies the error message. You can search for the unique identifier in the Javadoc reference pages to see an explanation of the content of the error message.

• Parameters - Placeholders for the specific classes, methods, and qualifiers that are cited in the exception message.

Example 9-1 Parts of an Error Message

The MOF compiler returns the following error:

REF_REQUIRED = Association class CIM_Docked needs at least two refs. 
Error in line 12.

• REF_REQUIRED is the unique identifier.

• CIM_Docked is a parameter.

• line 12 indicates the line number in the .mof file in which the error occurred.

WBEM Error Messages

This section describes the WBEM error messages, sorted by unique identifier.

ABSTRACT_INSTANCE

Description: This error message uses one parameter, {0}, which is replaced by the name of the abstract class.

Cause: A create instance was attempted for the instance. However, the specified class is an abstract class, and abstract classes cannot have instances.

Solution: Create instances for concrete classes.

CANNOT_ASSUME_ROLE

Description: This error message uses two parameters:

• {0} is replaced by the user name.

• {1} is replaced by the role name.

Cause: The specified principal cannot assume the specified role.

Solution: Make sure that the user has the appropriate rights to assume the given role. If the user does not have the appropriate rights, contact your system administrator.

CHECKSUM_ERROR

Description: This error message does not use parameters.

Cause: The message could not be sent because the message was damaged or was corrupted. The damage could have occurred accidentally in transit or by a malicious third party.

---

Note - This error message is displayed when the CIMOM receives an invalid checksum. A checksum is the number of bits in a packet of data that were passed over the network. This number is used by the sender and the receiver to ensure that the data has not been corrupted or intentionally modified during transit. This number also used by the sender and receiver of the information to verify that the transmission is secure.

An algorithm is run on the data before transmission. Then the checksum is generated and included with the data to indicate the size of the data packet. When the message is received, the receiver can recompute the checksum and compare the result to the sender's checksum. If the checksums match, the transmission was secure, so the data was not corrupted or modified.

---

Solution: Resend the message using the security features of Solaris WBEM Services. For information about using these features of Solaris WBEM Services, see Chapter 8, Administering Security.

CIM_ERR_ACCESS_DENIED

Description: This error message does not use parameters.

Cause: This error message is displayed when a user does not have the privileges and permissions necessary to complete an action.

Solution: Request privileges to complete the operation from your system administrator or the person who is responsible for your CIMOM.