N1 Provisioning Server 3.1, Blades Edition, System Administration Guide

Monitoring Errors (ID 4015 through 4042)


4015
Monitoring [start] Error: No database connection.
Description:

The database connection is unavailable now.

Solution:

Check the CPDB connection and redo the operation.


4016
Monitoring [start] Error: No farm id.
Description:

The farm ID is not valid. The CPDB has incorrect values for this farm.

Solution:

Contact http://sun.com/service/contacting/index.html for assistance.


4017
Monitoring [start] Error: No node id.
Description:

The node ID is not valid. The CPDB has incorrect values for this node.

Solution:

Contact http://sun.com/service/contacting/index.html for assistance.


4019
Monitoring [start] Warning: Empty MML.
Description:

The Monitoring Markup Language (MML) file is empty.

Solution:

This message is associated with the farm's MML. Contact http://sun.com/service/contacting/index.html for assistance.


4022
Monitoring [start] Error: Database error occurred (exception details).
Description:

A database error occurred while accessing MML from the CPDB.

Solution:

Contact http://sun.com/service/contacting/index.html for assistance.


4024
Monitoring [start] Error: Error occurred (exception-details).
Description:

A monitoring exception occurred.

Solution:

View details of the message, then contact http://sun.com/service/contacting/index.html for assistance.


4028
MML Parsing Error: Parsing error occurred (exception details).
Description:

The MML is invalid.

Solution:

This message is associated with the farm's MML. Contact http://sun.com/service/contacting/index.html for assistance.


4029
MML Parsing Error: I/O error occurred (exception-details).
Description:

An I/O error occurred during parsing of the MML.

Solution:

View details of the message, then contact http://sun.com/service/contacting/index.html for assistance.


4030
MML Parsing Error: MML content is empty.
Description:

The MML is empty.

Solution:

Contact http://sun.com/service/contacting/index.html for assistance.


4033
MML Parsing Warning: Invalid threshold value threshold-volume
Description:

The MML is wrong.

Solution:

This message is associated with the farm's MML. Contact http://sun.com/service/contacting/index.html for assistance.


4034
MML Parsing Warning: Illegal node-name child node node-ID found.
Description:

The MML is wrong.

Solution:

This message is associated with the farm's MML. Contact http://sun.com/service/contacting/index.html for assistance.


4035
MML Parsing Warning: Invalid monitor monitor-name encountered.
Description:

The MML is wrong.

Solution:

This message is associated with the farm's MML. Contact http://sun.com/service/contacting/index.html for assistance.


4036
MML Parsing Warning: No value for integer.
Description:

The MML is wrong.

Solution:

This message is associated with the farm's MML. Contact http://sun.com/service/contacting/index.html for assistance.


4037
Remote Command for shutdown invoked successfully, but shutdown has a problem, 
   check the console for device device-ID
Description:

The system in unable to shut down the resource pool server.

Solution:

Ensure that the server can be pinged and the N1 Provisioning Server agent is active.


4038
Shutdown of device device-ID failed. Interrupted exception while pinging the device.
Description:

The Java Virtual Machine (JVM) is unable to execute sleep mode while waiting for the device to be stopped.

Solution:

Contact http://sun.com/service/contacting/index.html for assistance.


4039
MML Parser Error: Cannot create parser with requested configuration 
   (parser-configuration_ exception)
Description:

An error exists in the MML.

Solution:

Contact http://sun.com/service/contacting/index.html for assistance.


4040
MML Parser Warning: The object warning has an invalid value (threshold)
Description:

An error exists in the MML.

Solution:

Contact http://sun.com/service/contacting/index.html for assistance.


4042
Monitoring [start] Error: Illegal access error occurred (illegal_access_exception)
Description:

Unable to open the connection to the CPDB.

Solution:

Ensure that the CPDB is running and accessible.