This section explains the 679XX message series.
[Virtual Edition]
Description
A timeout error occurred during execution of the command.
Corrective Action
If this message is displayed during execution of the backup or the restore commands for manager resources of the admin server
There are the following two possibilities:
Operations being executed on the admin server remain in the database
The manager has been stopped or started during execution of the command
Take the following corrective actions for each command:
When the rcxbackup command, the scwbackup command, or the rcxkeydefbackup command has been executed
Start the manager to complete the operations being executed on the admin server, or perform the operation again after restoring the collected configuration definition information.
Check that stopping or starting of the manager has not been performed, and then perform the operation again.
When the rcxrestore command, the scwrestore command, or the rcxkeyrestore command has been executed
Check that stopping or starting of the manager has not been performed, and then perform the operation again.
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
If this message is displayed during the following operations, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
VM Host
- Registration
- Release
For cases other than the above
Collect troubleshooting information and contact Fujitsu technical staff.
[Cloud Edition]
Description
A timeout error occurred during command execution.
Corrective Action
When this message is displayed during execution of the backup and restore command for the manager properties of admin server, one of the following may apply:
An operation being executed on the admin server remains in the database
The manager was stopped or started during command execution
Perform the following corrective actions for each command:
When the rcxbackup command, the scwbackup command, or the rcxkeydefbackup is executed
Start the manager and complete the operation being executed on the admin server, or restore the configuration definition information already collected, then perform the operation again.
Check that stopping or starting of the manager has not been performed, and then perform the operation again.
When the rcxrestore command, the scwrestore command, or the rcxkeyrestore command has been executed
Check that stopping or starting of the manager has not been performed, and then perform the operation again.
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
If this message is displayed during the following operations, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
Physical L-Servers
Image Operations
Registration
Deletion
Usage Changes
Power Operations
Conversion
Reversion
VM Hosts
Registration
Release
Perform the following action, when VM type of a virtual L-Server is "OVM-SPARC", or this message is displayed when a VM guest is migrated.
Perform the "Procedure that restores the preset value of "auto-boot?"" of "Message number 67375".
When the VM type corresponds to the following conditions at the time of OVM for SPARC virtual L-Server creation, the serial L-Server creation process has failed.
When multiple L-Servers with a Solaris 11 image specified are created simultaneously
"true" is specified in the "Operation mode definition file for when simultaneously creating multiple L-Servers with a Solaris 11 image specified" in "8.8.1 Creating Definition Files" in the "Setup Guide CE"
A possible cause of the failure is that simultaneous creation of multiple L-Servers may not have finished. Refer to "3.7 Creation of a Virtual L-Server Does not Finish even after a Long Time." in "Troubleshooting", and check that there are no processes which have not finished after a long time.
When the created guest domain is not deleted, delete it referring to "Deletion procedure for guest domains" given in "Message number 67373".
[Virtual Edition] [Cloud Edition]
Description
An unknown error may have occurred in communication with the services of the Resource Coordinator manager on the admin server.
Corrective Action
Collect the relevant message and troubleshooting data, and contact Fujitsu technical staff.
Information
System Log Messages
The messages that are output to the system log on the admin server are as follows:
Messages with the "application log" event type
Messages with source names starting with "JSE_SWRC_FJSVRCX"
[Virtual Edition]
Description
An internal error occurred during execution of the command.
Corrective Action
This message may be output after execution of the rcxadm command is canceled by pressing [Ctrl+C].
Corrective action is not necessary because the execution has been canceled correctly.
When this message is displayed after execution of the command for obtaining the troubleshooting information, note down the displayed message and contact Fujitsu technical staff.
The detailed message may be output in the OS system log.
Check the message number displayed in the system log and take corrective action.
Resource Orchestrator may have been installed in the wrong location.
Reinstall using the correct paths given in the following sections:
Installation location for managers
"2.1.1.6 Installation" in the "Setup Guide VE"
Installation location for agents
"2.2.2 Installation [Windows] [Hyper-V]" in the "Setup Guide VE"
When details is "Service control timeout. service_name=Resource Coordinator Manager". [Windows Manager]
Check that the SNMP Trap Service, which is required software for managers, has been configured correctly.
For details on the configuration, refer to "2.1.1.2 Software Preparation and Checks" in the "Setup Guide VE".
When details is "Service control timeout. service_name=ResourceCoordinatorWebServer(Apache)". [Windows Manager]
Check that Microsoft Visual C++ 2008 Redistributable Package (x86) or Microsoft Visual C++ 2010 Redistributable Package (x86), which is required software of the manager, has been installed.
When backup or restore has been performed for manager resources of the admin server
The manager may have been stopped or started during execution of the command.
Check that the manager is not stopped or not started, then perform the operation again.
There is a possibility that the database could not be accessed.
Execute the command again.
This message may be output after execution of the command is canceled by pressing [Ctrl+C].
Corrective action is not necessary because the execution has been canceled correctly.
When management software (ISM) has been registered
When there is an issue such as being unable to communicate with ISM, ISM may not operate normally.Reconfigure the settings so that ISM operates normally.
When the warning event [A desktop heap allocation failed.] with [Source: Win32k Event ID: 243] is displayed in the system event log
For the following OSs, allocation of the OS memory size, which is referred to as the desktop heap, failed.
Windows Server 2008
Windows Server 2012
Windows Server 2016
For the corrective action, refer to "13.1 When the Desktop Heap is Exhausted" in "Troubleshooting".
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Cloud Edition]
Description
An error occurred in the following cases:
Either an internal error has occurred or the XML file specified during the following operations has been loaded:
L-Server Creation or Configuration Modification
Importing an L-Server template
Importing for DR
Creating network resources
When the command for backup and restore for manager properties of an admin server has already been executed
When executing reflection of server NIC definition (rcxadm nicdefctl commit)
When creating, modifying, or deleting network resources or when creating an L-Platform (including firewalls or server load balancers) or modifying its configuration, with auto-configuration for network devices enabled
When collecting cloning images using a virtual L-Server with the VM Type "RHEL-Xen"
Collection of the cloning image failed.
In other cases
An internal error occurred during execution of the command.
Corrective Action
When executing the following operations:
L-Server Creation or Configuration Modification
Importing an L-Server template
Importing for DR
Creating network resources
Review the content of the XML specified during operations, then perform the operation again.
When backup or restore has been performed for manager resources of the admin server
The manager may have been stopped or started during execution of the command.
Check that the manager is not stopped or not started, then perform the operation again.
There is a possibility that the database could not be accessed.
Execute the command again.
This message may be output after execution of the command is canceled by pressing [Ctrl+C].
Corrective action is not necessary because the execution has been canceled correctly.
When executing reflection of server NIC definition (rcxadm nicdefctl commit)
The contents of Resource Orchestrator are not correct. Collect the relevant message and troubleshooting data, and contact Fujitsu technical staff.
When creating, modifying, or deleting network resources or when creating an L-Platform (including firewalls or server load balancers) or modifying its configuration, with auto-configuration for network devices enabled
The process which executes the script may have failed to start, or the process being executed may have been aborted.
Collect the relevant message and troubleshooting data, and contact Fujitsu technical staff.
When details is "Service control timeout. service_name=Resource Coordinator Manager". [Windows Manager]
Check that the SNMP Trap Service, which is required software for managers, has been configured correctly.
For details on the configuration, refer to "2.1.1.2 Software Preparation and Checks" in the "Setup Guide CE".
When details is "Service control timeout. service_name=ResourceCoordinatorWebServer(Apache)". [Windows Manager]
Check that Microsoft Visual C++ 2008 Redistributable Package (x86) or Microsoft Visual C++ 2010 Redistributable Package (x86), which is required software of the manager, has been installed.
When collecting cloning images using a virtual L-Server with the VM Type "RHEL-Xen"
The character string specified for the -name option when collecting the cloning image may exceed the specifiable number of characters. Specify the name correctly and perform the operation again.
For details on the -name option, refer to "4.1 rcxadm image" in the "Reference Guide (Command/XML) CE".
In other cases
This message may be output after execution of the rcxadm command is canceled by pressing [Ctrl+C].
Corrective action is not necessary because the execution has been canceled correctly.
When this message is displayed after execution of the command for obtaining the troubleshooting information, note down the displayed message and contact Fujitsu technical staff.
The detailed message may be output in the OS system log.
Check the message number displayed in the system log and take corrective action.
Resource Orchestrator may have been installed in the wrong location.
Reinstall using the correct paths given in the following sections:
Installation location for managers
"2.1.1.6 Installation" in the "Setup Guide CE"
Installation location for agents
"2.2.2 Installation [Windows] [Hyper-V]" in the "Setup Guide CE"
When management software (ISM) has been registered
When there is an issue such as being unable to communicate with ISM, ISM may not operate normally.
Reconfigure the settings so that ISM operates normally.
When the warning event [A desktop heap allocation failed.] with [Source: Win32k Event ID: 243][Event Source: Win32k Event ID: 243] is displayed in the system event log [A desktop heap allocation failed.]
For the following OSs, allocation of the OS memory size, which is referred to as the desktop heap, failed.
Windows Server 2008
Windows Server 2012
Windows Server 2016
For the corrective action, refer to "13.1 When the Desktop Heap is Exhausted" in "Troubleshooting".
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
