This section explains the 672XX message series.
[Description]
Command execution was canceled. For details, refer to the event output at the same time.
[Corrective Action]
Refer to the event output at the same time.
[Description]
Deletion of the cloning image obj failed.
[Corrective Action]
Refer to the other messages output at the same time.
[Description]
The IP address or MAC address specified for obj cannot be used because it is already in use.
[Corrective Action]
Check and correct the option argument specified, and then perform the operation again.
When this message is output, the IP address or MAC address may already be being used for one of the following registered devices.
Chassis
LAN switches
Admin servers
Managed servers
Power monitoring devices
[Description]
The command cannot be executed because another command is being executed by obj.
In the following cases, a resource name other than the one specified is displayed for obj.
When power operation of a chassis is performed while another process is being executed for a resource mounted in the chassis
When takeover of operations has been performed for a server which has been switched to a spare server and there is another physical OS or VM host that has the server configured as a spare server, and that physical OS or VM host is executing another process
[Corrective Action]
Check the object obj and perform the operation again after the other command is complete.
However, when performing registration or deletion of managed servers or LAN switches in the same chassis, commands can only be performed for one resource at a time. This message will be displayed when commands are performed for multiple resources at the same time.
[Description]
image has already been defined.
[Corrective Action]
Check and correct the object, then perform the operation again.
[Description]
Cloning images have not been defined.
[Corrective Action]
When this message is output during cloning image operation, collect the cloning image and then execute the command again.
[Description]
The system image of the managed server or the system image of the version specified does not exist.
[Corrective Action]
Check the system image of the relevant managed server.
If the specified version is incorrect, specify the correct version and execute the command again.
In some cases the image file may not have been synchronized. For details, refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide" and restart the manager service.
[Description]
The cloning image has already been deployed to the managed server server_name.
[Corrective Action]
Check and correct the relevant managed server, then perform the operation again.
[Description]
The specified servers include servers with different settings.
[Corrective Action]
Check the following settings for the target server.
Whether there are settings for HBA address rename
Whether there is server management software being used
Target servers with the same settings and perform the operation again.
For servers with different settings, process them individually.
[Description]
There is no spare server that matches the following conditions. Or the spare server specified does not meet the following conditions.
Power control is possible
The status is "normal", "warning", or "stop"
When the spare server is a VM host, it must meet all of the following conditions:
HBA address rename settings are configured, and an agent is registered
The status is "normal" or "warning"
A VM guest does not exist on a VM host (when the settings are not configured to switch to a spare server containing a VM guest)
[Xen]
It is not configured as the pool master (when the VM host is Citrix XenServer)
The server is not set as the switchover target for another switchover event
The server belongs to the same subnet as the operation server
[Corrective Action]
Choose one of the following corrective actions:
After checking there is a spare server that matches the above conditions, perform the operation again.
Specify a spare server that meets the above conditions, and then perform the operation again.
Specify a managed server that meets the above conditions as the spare server for use in server switchover, and then perform the operation again.
When setting a VM host as a spare server using the pre-configuration function, do so after importing HBA address rename settings and agent registration.
For details, refer to "7.2 Importing the System Configuration File" of the "ServerView Resource Coordinator VE Setup Guide".
[Description]
obj has not been recovered.
Takeover of operations was executed on managed servers that have not performed Auto-recovery or manual switching.
[Corrective Action]
There is no need to take corrective action, as neither Auto-recovery nor manual switching to the managed server specified has been performed.
[Description]
The command cannot be executed because a public IP address has not been assigned.
[Corrective Action]
Check if installation of the software has been completed successfully.
For how to install software, refer to "6.2 Configuring the Operating Environment of Managed Servers" of the "ServerView Resource Coordinator VE Setup Guide".
[Description]
The IP address specified is invalid.
[Corrective Action]
When this error occurs during the registration of a managed server
Check that the admin LAN IP address of the specified managed server is included in the subnet of the admin LAN, and then perform the operation again.
When this error occurs when changing the admin IP address of a managed server
Check the following and perform the operation again.
That the admin LAN IP address of the specified managed server is included in the subnet of the admin LAN
That IP addresses before and after changing are in the same subnets, when changing the admin IP addresses for a primary server or a spare server.
When this error occurs when changing the admin LAN IP address of an admin server
Check that the IP address specified is the admin LAN IP address of the admin server, and then perform the operation again.
[Description]
The range of IP addresses defined on the admin server is already in use.
[Corrective Action]
Check the range of the IP addresses (DHCP range) defined on the admin server.
[Description]
An error has occurred on the admin server.
[Corrective Action]
Check the following:
If setup of the admin server was completed successfully.
For setup, refer to "2.1 Manager Installation" of the "ServerView Resource Coordinator VE Installation Guide".
Whether communication with the server management unit is possible.
Use the ping command or another method to check if there is a problem with the network environment between the admin server and the server management unit.
If a cable is disconnected from the LAN connector, connect it.
Whether Write (reference and updating) authority is possessed for the SNMP setting of the management blade.
Check the SNMP community name set from the RC console.
If it was omitted, "public" will be specified.
Check that the management blade of the managed server has Write (reference and updating) authority for the SNMP community name specified.
If the SNMP community name does not have Write (reference and updating) authority, change the authority settings.
Check that the values of the IP address, user name, and password set for the Remote Management Controller when registering the managed server have not been changed from their original values.
For details of checks and the setup method, refer to the manual of the server being used.
Refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide", and check whether the "Related services" have been started on the admin server. If they have stopped, restart them.
For how to stop and start the services, refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide".
After starting any stopped services, perform the operation that resulted in the error again.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Acquisition of managed server information failed because the server cannot communicate with the managed server or server management unit.
[Corrective Action]
Check the status of the managed server and the server management unit, the value specified for the operand, and the values set for the following:
That the IP address of the server management unit of the managed server is set correctly and the server is operating normally
The SNMP community settings of server management unit for the managed server
That the SNMP community name specified from the RC console has Read (reference authority) or Write (reference and updating) authority
The SNMP community settings of the managed server
That the SNMP community name of the managed server has Read (reference authority).
Specify the same SNMP community name for the managed server and the server management unit.
That the values of the IP address, user name, and password set for the Remote Management Controller when registering the managed server have not been changed from their original values
That the IP address of the managed server specified is correct
Setup of the agent for the specified managed servers was completed successfully
Network settings (such as DNS) of the admin server are correct and the execution of OS network-related commands is completed within seconds
When this message is displayed after reconfiguration of hardware properties following replacement, and there are no problems with the managed server or server management unit, there is a possibility that the reconfigured hardware properties were temporarily unobtainable.
Reconfigure the hardware properties again.
When this message is displayed during the deployment of cloning images, registration of agents after deployment has failed. Either redeploy the cloning image or refer to step 2. in the corrective action of "Message number 67328" and recover the managed server the image was deployed to.
When a single cloning image was being deployed to multiple managed servers, take corrective action for all of the managed servers.
When a managed server is VMwareESXi, necessary information cannot be obtained from the required software.
Refer to ServerView Operations Manager in "1.1.2.2 Required Software" of the "ServerView Resource Coordinator VE Installation Guide", and enable management of the target server using ServerView Operations Manager.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
An error has occurred during power control of a managed server.
[Corrective Action]
Check the following and take corrective action.
Check the SNMP community name set from the RC console.
If it was omitted, "public" will be specified.
Check that the management blade of the managed server has Write (reference and updating) authority for the SNMP community name specified.
If the SNMP community name does not have Write (reference and updating) authority, change the authority settings.
Check that the values of the IP address, user name, and password set for the Remote Management Controller when registering the managed server have not been changed from their original values.
For details of checks and the setup method, refer to the manual of the server being used.
[Description]
The chassis has not been registered.
The admin LAN of the chassis including the server to be registered may not have been set correctly.
[Corrective Action]
After registering a chassis, perform the operation again.
When the chassis has been registered, check the admin LAN settings of the server to be registered.
[Description]
The managed server specified does not meet the requirements for Auto-recovery or manual switching.
The name of the managed server specified is displayed for obj.
The following detailed causes are displayed for detail.
no image
Backup of the system image of the server specified was not performed.
[Corrective Action]
Take corrective action based on the detailed cause.
no image
After system images are backed up on the server specified, perform manual switching again.
[Description]
A Resource Coordinator VE agent has not been installed on a managed server.
The name of the managed server is displayed for obj.
[Corrective Action]
After installing a Resource Coordinator VE agent on the managed server, execute the command again.
[Description]
An error has occurred in LAN switch control.
The network management command is displayed for command.
A character string indicating the process that resulted in an error during network management is displayed for rcxerrno.
One of the following is displayed for mip:
The admin IP addresses of the managed LAN switch
Admin IP addresses or server names of managed servers
An error may occur during the following conditions:
When specifying a different IP address with LAN switch
When specifying a SNMP community name not set in the LAN switch
When the LAN switch is not operating correctly
When the LAN switch is replaced with a different type of LAN switch from the original, and restoration performed
[Corrective Action]
After checking the following, execute the command again.
That the LAN switch is a supported model
That the LAN switch is the same model as the original
Whether the content of the following settings of LAN switch matches that of Resource Coordinator VE
If they are different, correct the settings of both LAN switch and Resource Coordinator VE so they match.
The admin IP addresses of LAN switch
The subnet mask for the admin IP addresses of the LAN switch
VLAN ID to which the admin IP addresses of the LAN switch belong
The connection port for the admin IP addresses of the LAN switch
SNMP community name
The user name for remote login
The password for remote login
The privileged password for remote login
Whether there is an abnormality in the communication route between the admin LAN and the LAN switch
Check whether a LAN cable is unplugged or the LAN switch is powered off.
Whether the LAN switch is operating correctly
Check the following, and if necessary, remove the problem using the maintenance procedure of the LAN switch.
The LAN switch is powered on
The SNMP agent is operating normally
The server can connect to the LAN switch using telnet
Information
When telnet connection is disabled, enable it.
For details on settings, refer to the manual for the server.
The number of simultaneous connections using telnet may be limited depending on the model. In this case, log out of other telnet connections.
[Description]
An internal command for obtaining server information may be being executed in another process.
[Corrective Action]
Wait a couple of minutes and then execute the command again.
[Description]
Command execution failed on the managed server.
The admin IP address of the managed server or the server name is displayed for mip.
[Corrective Action]
Check the following on the managed server indicated for mip.
Check that the managed server is not down. If the system is down, start the system from the appropriate OS.
Check that the managed server was started using the appropriate OS. If it was not, change the BIOS settings referring to the manual for the server.
[Linux]
Check if the LAN card is correctly configured and activated on the system by executing the /sbin/ifconfig -a command. If it is not configured and activated correctly, configure the LAN card referring to the Linux installation guide.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
An error has occurred in VLAN settings for LAN switch.
[Corrective Action]
For the LAN switch of the managed server that was the target of the operation (such as server registration or server deletion) that resulted in the error, confirm the following.
The LAN switch is powered on
The SNMP agent is operating normally
The server can connect to the LAN switch using telnet
Information
When telnet connection is disabled, enable it.
For details on settings, refer to the manual for the server.
The number of simultaneous connections using telnet may be limited depending on the model. In this case, log out of other telnet connections.
After checking the above, if necessary, remove the problem using the maintenance procedure of the LAN switch.
Then, Refer to "Replacing LAN switch blades" in "9.6 Replacing Non-server Hardware" of the "ServerView Resource Coordinator VE Operation Guide" and reflect the VLAN information on the server, then perform the operation again.
[Description]
PRIMECLUSTER GLS has not been installed on the managed server.
[Corrective Action]
Install PRIMECLUSTER GLS on the managed server.
Refer to the product manual for the installation method of PRIMECLUSTER GLS.
[Description]
The command terminated abnormally.
[Corrective Action]
Perform the operation again.
[Description]
Password decryption failed.
[Corrective Action]
If this message is displayed when importing a system configuration file, check that the password for the resource definition specified as "encrypted"(an encrypted password) has been configured as an encrypted character string.
For the system configuration file, refer to "Appendix D Format of CSV System Configuration Files" of the "ServerView Resource Coordinator VE Setup Guide".
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
The range of IP addresses specified is incorrect.
code is identified as follows:
9: An invalid IP address is included in the specified range of IP addresses 10: The range of the start IP address and that of the end IP address are incorrect 13: The start IP address and end IP address are not in the same subnet 14: The start IP address is the same as the subnet number 15: The end IP address is the same as the broadcast address 102: The host of the start IP address specified for the redundancy method is not the same 103: The same subnet of the start IP address specified for the redundancy method has been used 201: IP addresses of registered managed servers exist outside the range of specified admin IP addresses, or a different subnet was specified when registered managed servers already exist.
[Corrective Action]
Take corrective action for the content displayed for code.
For "201"
Choose one of the following corrective actions:
Specify a range of addresses including the registered managed server addresses in the same subnet as the range of admin IP addresses prior to change, and then perform the operation again.
Release the IP addresses of the registered managed servers, and then perform the operation again.
For a code other than the above
Check the parameter, and then perform the operation again.
[Description]
The option specified option is not supported.
[Corrective Action]
Check and correct the option specified, and then perform the operation again.
[Description]
Deletion of the oldest cloning image failed because it is in use.
[Corrective Action]
Delete one or more cloning images that are not in use, then perform the operation again.
[Description]
Deleting the version version of the cloning image failed because it is in use.
[Corrective Action]
Enable use of the specified version version of the cloning image, and then perform the operation again.
[Description]
An error has occurred during the process set in "8.6 Network Parameter Auto-Configuration for Cloning Images" of the "ServerView Resource Coordinator VE Setup Guide".
A number corresponding to one of the following processes is displayed for type:
10: PRE_TGTSVR_IMAGE_CREATE(the process before collection of cloning images)
11: POST_TGTSVR_IMAGE_CREATE(the process after collection of cloning images)
13: POST_TGTSVR_IMAGE_INSTALL(the process after deployment of cloning images)
[Corrective Action]
Take the corrective action for "Message number 61501" or "Message number 61502" displayed in the event log.
When neither "Message number 61501" nor "Message number 61502" are displayed, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Login failed.
[Corrective Action]
Enter the correct user name and password, then log in again.
When there is no error in the user name and password, and the management account is a new addition, there is an error in the password configured during account creation.
Set the password given in "4.2 Managing User Accounts" of the "ServerView Resource Coordinator VE Operation Guide" again.
[Description]
Writing to the file or directory specified for filename failed because the file type is invalid.
[Corrective Action]
After performing one of the following corrective actions perform the operation again.
Change the name of the file or directory displayed for filename
Move or delete the file or directory displayed for filename
[Description]
The environment variable variable is invalid.
[Corrective Action]
Check the value of the variable variable and then perform the operation again.
[Description]
The shell to be started was not found.
[Corrective Action]
Correct the environment variable SHELL.
[Description]
Execution of the command described in obj failed.
[Corrective Action]
Check the following, resolve the problem and execute the command again.
The command execution environment is correct.
Execute the /opt/FJSVrcvhb/bin/rcxhbactl command from a desktop environment.
Users have sufficient command execution authority
There is enough free memory
[Description]
The file or directory specified for filename was not found.
[Corrective Action]
Specify the correct file or directory.
[Description]
The file or directory specified for filename cannot be created.
[Corrective Action]
Check the access authority for the directory.
[Description]
There is no home directory for the executing user.
[Corrective Action]
For the OS user account on which the command has been executed, check if the following has been set and the directory set is on the admin server. Correct them and perform the operation again.
There is an entry of the user account on which the command has been executed on "Local Users and Groups" of the admin server
In the environment valuable of the above account, APPDATA or USERPROFILE exists and the correct directory is set
[Description]
The chassis chassis_name was not found.
[Corrective Action]
Check the name of chassis specified.
[Description]
The specified alias(alias) was not found.
[Corrective Action]
Execute the following command and check the alias, and then perform the operation again.
[Windows]
>rcxadm certctl list <RETURN> |
[Linux]
# rcxadm certctl list <RETURN> |
Example
In the following, client2, client1, server5, server4, server3, server2, and server1 are aliases.
Truststore: |
[Description]
The keystore file was not found.
[Corrective Action]
Check that the keystore file exists in the following directory.
When operating managers in clusters, check that the shared disk for managers is mounted, and then perform the operation again.
If it does not exist, collect troubleshooting information and contact Fujitsu technical staff.
When it is a manager
[Windows]
Installation_folder\Manager\etc\opt\FJSVssmgr\current\certificate\common_truststore
[Linux]
/etc/opt/FJSVrcvmr/opt/FJSVssmgr/current/certificate/common_truststore
When it is an agent
[Windows/Hyper-V]
Installation_folder\Agent\StorageRM\Agent\etc\certificate\agent_truststore
[Linux/VMware/Xen]
/etc/opt/FJSVssagt/certificate/agent_truststore
[Solaris]
/etc/opt/FJSVrcvat/certificate/agent_truststore
[Description]
The keystore file may be damaged or the file is incorrect.
[Corrective Action]
Collect troubleshooting information and contact Fujitsu technical staff.
[Description]
An internal error occurred.
[Corrective Action]
Collect troubleshooting information and contact Fujitsu technical staff.
[Description]
The command syntax is incorrect. "usage" is displayed.
[Corrective Action]
Check and correct the command format, and then perform the operation again.
[Description]
The object obj does not support function.
The name of the unsupported function is displayed for function.
When function cannot be used for obj, detail will not be displayed.
When function cannot be used because of usage conditions, the following detailed information will be displayed enclosed in brackets for detail.
"Out of DHCP range"
The IP address displayed in obj is out of the range of IP addresses for which the backup and restore functions for system images can be used.
"invalid switchover method"
Server switchover using backup and restore cannot be used for the server displayed for obj.
This is displayed when a VM host is operating on the server displayed for obj.
"invalid model"
The target of operation displayed for obj is a model that does not support function.
"invalid destination"
The VM guest displayed for obj does not support movement to the VM host specified as the destination.
"VM type"
The target of operation displayed for obj is server virtualization software that does not support function.
[Xen]
Setting and release of VM maintenance mode for Citrix XenServer pool masters is not supported.
"OS type"
The target of operation displayed for obj is a server OS that does not support function.
"incompatible network devices"
The NIC configuration of the target of operation displayed for obj does not match the conditions for spare servers of function.
"incompatible IBP group configuration between switch-1 and switch-2"
The IBP group settings of the switch switch-1 of the switchover source, and the switch switch-2 of the switchover target that is displayed for obj do not match the operation conditions of function.
"incompatible mode between switches switch-1 (mode-1) and switch-2 (mode-2)"
The modes of the switch switch-1 of the switchover source, and the switch switch-2 of the switchover target that is displayed for obj do not match.
The modes of each switch, "IBP mode" or "switch mode" are displayed for mode-1 and mode-2.
"VIOM"
As the server displayed for obj already has VIOM coordination configured as its virtualization method, HBA address rename cannot be set.
"invalid deployment configuration"
The function displayed for function is one not supported in the current environment. For details of backup and restore, and cloning, use ServerView Deployment Manager. For Virtual I/O (HBA address rename), please use ServerView Virtual-IO Manager.
When this message is displayed for other operations, it is not necessary to perform those operations.
For "difference of NIC setting for Admin LAN"
When the settings of the NIC for the admin LAN are a server different to that displayed for obj, configuration of a spare server is not possible.
[Corrective Action]
This message is displayed because use of an unsupported function was attempted for obj. No action is required.
[Description]
The specified command, subcommand, or option is not supported.
The name of the managed server or the port name is displayed for obj.
The following detailed information is given in detail.
"Manager"
The server displayed for obj is an admin server.
"Port name"
The port name displayed for obj is a port name not supported by Resource Coordinator VE.
[Corrective Action]
Perform checks based on each piece of detailed information, if the combination of resources is incorrect or the values differ, change the values specified or the settings and then perform the operation again.
"Manager"
When this message is displayed during registration of a managed server, check that an admin server is not the target of the operation.
If displayed when performing reconfiguration of hardware properties, check that an admin server has not been mounted in the relevant slot.
"Port name"
When changing port numbers, check there are no mistakes in port names.
For how to change port numbers, refer to "6.3.1.2 Changing Port Numbers" of the "ServerView Resource Coordinator VE Setup Guide", or "5.7 rcxadm mgrctl" of the "ServerView Resource Coordinator VE Command Reference".
[Description]
The specified managed server cannot perform operation against target.
The name of the managed server is displayed for server.
The target operation of server is displayed for target.
[Corrective Action]
Correct the specified target.
[Description]
An error has occurred because the PostgreSQL login user password has been changed.
[Corrective Action]
The configured user password is not correct.
Check the OS password setting conventions, and set an appropriate password.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
The command cannot be executed because the obj1 is defined as type of obj2.
[Corrective Action]
After resolving the problem, perform the operation again.
[Description]
The VM host or VM guest is not supported.
The name of the specified server is displayed for obj.
[Corrective Action]
Specify the physical OS name, and then perform the operation again.
[Description]
The IP address specified is incorrect, or the chassis information specified is not registered on the admin server.
[Corrective Action]
Check the following:
Check that the specified IP addresses of the chassis and server management unit or the server information (such as IP address) are correct.
If there are errors, perform registration again using the correct information.
Check if the chassis is powered on. If the chassis is not powered on, after powering it on, perform the operation again.
[Description]
The LAN switch for connection to the network interface of the managed server for registration is not registered.
[Corrective Action]
Register the LAN switch for connection to the network interface of the managed server for registration, and then perform the operation again.
How to check and register the destination LAN switch
Refer to "Appendix B Connections between Server Network Interfaces and LAN Switch Ports" of the "ServerView Resource Coordinator VE Setup Guide", and check the LAN switch to be connected to the NIC of the specified managed server.
Refer to "D.3 Resource Definitions" of the "ServerView Resource Coordinator VE Setup Guide", add LAN switch definitions to the system configuration file, and then import it again.
[Description]
The slot number or IP address of the specified LAN switch is incorrect.
[Corrective Action]
Check the mounting position of the LAN switch blade and IP address, specify the correct slot number and IP address, and then perform the operation again.
[Description]
There are multiple resources with the name specified for obj.
Commands cannot be used to operate multiple resources with the same name.
[Corrective Action]
Execute the command after changing the names of resources so no two have the same name.
When it is not possible to change the names of resources with the same name, perform operations from the GUI.
[Description]
Login as a Resource Coordinator VE user has not been performed.
[Corrective Action]
Perform the operation again after logging in as a Resource Coordinator VE user.
If this message is displayed when executing a command, log in as an administrative user of Resource Coordinator VE or with OS administrator authority and perform the operation again.
For details of the authority necessary for executing commands, refer to "Chapter 1 Overview" of the "ServerView Resource Coordinator VE Command Reference".
For details of how to log in as an administrative user of Resource Coordinator VE, refer to "2.1 rcxlogin" of the "ServerView Resource Coordinator VE Command Reference".
When operating managers in clusters, there is a chance that the shared disk for managers is not mounted.
Mount the shared disk for managers on the node the operation was performed on and perform the operation again.
[Description]
A communication error with the manager occurred during execution of a command.
[Corrective Action]
Check the following, resolve the problem and execute the command again.
Check the network environment
How to check
Check that the port number (service name: rcxweb, default: 23461) used by the admin server for the Resource Coordinator Manager service is not being used for another service.
Execute the following command on the server where a manager is installed to check the usage status of the port number.
Display process IDs using port numbers
Example
[Windows]
>netstat -oan | find "0.0.0.0:23461" <RETURN> TCP 0.0.0.0:23461 0.0.0.0:0 LISTENING 2632 -> Process ID is 2632 |
[Linux]
# netstat -lnp | grep ":23461" <RETURN> tcp 0 0 :::23461 :::* LISTEN 4095/httpd -> Process ID is 4095 |
Check that the process ID belongs to the httpd of Resource Coordinator VE
Example
[Windows]
>tasklist /svc /FI "PID eq 2632" <RETURN> Image name PID service ========================= ====== ====================================== httpd.exe 2632 ResourceCoordinatorWebServer(Apache) |
[Linux]
# ps -fp 4095 <RETURN> UID PID PPID C STIME TTY TIME CMD root 4095 1 0 Jul18 ? 00:00:00 /opt/FJSVrcvmr/sys/apache/bin/httpd -k start |
Corrective action
When it was being used by another service, change the port number to be used.
For how to change port numbers, refer to "6.3.1.2 Changing Port Numbers" or "6.3.2.6 Changing Port Numbers" of the "ServerView Resource Coordinator VE Setup Guide".
When the port number being used by Resource Coordinator Manager is correct, or the corrective action above does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
A console control error has occurred in the process in the rcxlogin command for hiding passwords.
[Corrective Action]
If terminal software other than the standard Windows command prompt is being used, check the settings of that software.
If the problem occurs when using the command prompt or the corrective action above does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Operation is not possible as the manager service is running.
The name of one of the running services is displayed for process.
[Corrective Action]
Refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide", and check whether the "Manager services" and "Related services" have been stopped on the admin server. If any server is running, stop it.
After stopping any started services, perform the operation that resulted in the error again.
[Windows]
When operating managers in clusters, there is a chance that the cluster services for the manager and for the HBA address rename setup service are online on the same node.
Check that the cluster services are not online on the same node in the [Failover Cluster Management] window, and migrate the cluster service for the HBA address rename setup service to another node if it is online on the same node.
When other nodes have failed, perform the operation after recovery.
