Top
Systemwalker Software Configuration Manager Message Guide
FUJITSU Software
Chapter 2 Message List > 2.7 Processes-related Messages
PreviousNext

2.7 Processes-related Messages

CFMGP00001 An error has occurred with the startup processing within the automated operation process for patch application. Detailed information={0}

Message Type

ERROR

Event Log

Yes

Description

The startup processing within the automated operation process has failed.

Parameter

{0}: Detailed information

Corrective Action

Check whether Systemwalker Software Configuration Manager is running correctly. If linked to ServerView Resource Orchestrator, check whether ServerView Resource Orchestrator is running correctly.

If it is running correctly, contact Fujitsu technical support.

CFMGP00002 An error has occurred with the initialization processing within the automated operation process for patch application. Detailed information={0}

Message Type

ERROR

Event Log

Yes

Description

The initialization processing within the automated operation process has failed.

Parameter

{0}: Detailed information

Corrective Action

Check whether Systemwalker Software Configuration Manager is running correctly. If linked to ServerView Resource Orchestrator, check whether ServerView Resource Orchestrator is running correctly.

If it is running correctly, contact Fujitsu technical support.

CFMGP00003 An error has occurred with the post-processing within the automated operation process for patch application. Keyword={0} Message={1} returnCode={2}

Message Type

ERROR

Event Log

Yes

Description

Post-processing has failed.

Parameter

{0}: Keyword
{1}: Message
{2}: Return value

Corrective Action

Some unnecessary files may remain undeleted, but they do not affect the system.

CFMGP00004 An error occurred during startup in the automated operation process that sets parameters. Detailed information={0}

Message Type

ERROR

Event Log

Yes

Description

Startup has failed in the automated operation process.

Parameter

{0}: Detailed information

Corrective Action

Check whether Systemwalker Software Configuration Manager is running correctly. If running correctly, contact Fujitsu technical support.

CFMGP00005 An error occurred during post-processing in the automated operation process that sets parameters. Keyword={0} Message={1} returnCode={2}

Message Type

ERROR

Event Log

Yes

Description

Post-processing has failed.

Parameter

{0}: Keyword
{1}: Message
{2}: Return value

Corrective Action

Some unnecessary files may remain undeleted, but they do not affect the system.

CFMGP00006 An error occurred during startup in the automated operation process that executes scripts. Detailed information={0}

Message Type

ERROR

Event Log

Yes

Description

Startup has failed in the automated operation process.

Parameter

{0}: Detailed information

Corrective Action

Check whether Systemwalker Software Configuration Manager is running correctly. If running correctly, contact Fujitsu technical support.

CFMGP00007 An error occurred during post-processing in the automated operation process that executes scripts. Keyword={0} Message={1} returnCode={2}

Message Type

ERROR

Event Log

Yes

Description

Post-processing has failed.

Parameter

{0}: Keyword
{1}: Message
{2}: Return value

Corrective Action

Some unnecessary files may remain undeleted, but they do not affect the system.

CFMGP00008 An internal error has occurred during process startup processing.

Message Type

ERROR

Event Log

Yes

Description

An internal error has occurred during process startup processing.

Corrective Action

Contact Fujitsu technical support.

CFMGP10000 Acceptance processing has completed normally.

Message Type

INFO

Event Log

No

Description

Acceptance processing has completed normally.

Corrective Action

No action is required.

CFMGP10001 Schedule standby is in progress.

Message Type

INFO

Event Log

No

Description

Schedule standby is in progress.

Corrective Action

No action is required.

CFMGP10002 The check to confirm that the server is operating has completed normally.

Message Type

INFO

Event Log

No

Description

The check to confirm that the server is operating has completed normally.

Corrective Action

No action is required.

CFMGP10003 Patch application processing has completed normally.

Message Type

INFO

Event Log

No

Description

The processing to apply patches has completed normally.

Corrective Action

No action is required.

CFMGP10004 Patch distribution processing has completed normally.

Message Type

INFO

Event Log

No

Description

The processing to distribute patches has completed normally.

Corrective Action

No action is required.

CFMGP10005 Parameter setting processing has completed normally. [Setting order:{0}][Software name:{1}][Version:{2}][Return value:{3}][Standard output:{4}][Standard error:{5}]

Message Type

INFO

Event Log

No

Description

The processing to set parameters has completed normally.

Parameter

{0}: Setting order
{1}: Software name
{2}: Version
{3}: Return value of parameter setting script
{4}: Standard output of parameter setting script
{5}: Standard error of parameter setting script

Corrective Action

No action is required.

CFMGP10006 Script execution has completed normally. [Return value:{0}][Standard output:{1}][Standard error:{2}]

Message Type

INFO

Event Log

No

Description

Script execution has completed normally.

Parameter

{0}: Return value of script
{1}: Standard output of script
{2}: Standard error of script

Corrective Action

No action is required.

CFMGP10007 OS restart processing has completed normally.

Message Type

INFO

Event Log

No

Description

The processing to restart the operating system has completed normally.

Corrective Action

No action is required.

CFMGP10008 Parameter setting processing has completed normally. Failed to obtain detailed results.

Message Type

WARNING

Event Log

No

Description

The processing to set parameters has completed normally. Acquisition of detailed results has failed.

Corrective Action

No action is required.

When checking the detailed results of parameter setting, check the log of the server for which parameters were set.

CFMGP10009 Schedule standby processing has completed normally.

Message Type

INFO

Event Log

No

Description

Schedule standby processing has completed normally.

Corrective Action

No action is required.

CFMGP10010 Restarting was not performed.

Message Type

INFO

Event Log

No

Description

Restarting was not performed.

Corrective Action

No action is required.

As restarting was not necessary after a patch was applied, restarting was not performed.

CFMGP10011 The command execution process has completed normally. [Return value:{0}][Standard output:{1}][Standard error:{2}]

Message Type

INFO

Event Log

No

Description

The command execution process has completed normally.

Parameter

{0}: Return value of the command
{1}: Standard output of the command
{2}: Standard error of script

Corrective Action

No action is required.

CFMGP10012 The file distribution process has completed normally.

Message Type

INFO

Event Log

No

Description

The file distribution process has completed normally.

Corrective Action

No action is required.

CFMGP10013 The file collection process has completed normally.

Message Type

INFO

Event Log

No

Description

The file collection process has completed normally.

Corrective Action

No action is required.

CFMGP20000 Failed to execute acceptance processing.

Message Type

ERROR

Event Log

No

Description

Acceptance processing has failed.

Corrective Action

  • Ensure that Systemwalker Software Configuration Manager is running. Refer to "Starting and Stopping Systemwalker Software Configuration Manager" in the Operation Guide for information on how to start Systemwalker Software Configuration Manager.

  • If the cause of the problem is other than the above, contact Fujitsu technical support.

CFMGP20001 Failed to confirm server operation. [Return value:{0}][Details:{1}]

Message Type

ERROR

Event Log

No

Description

Confirmation of server operation has failed.

Parameter

{0}: Return value
{1}: Details

Corrective Action

If the return value and details that are output are as follows, take the corresponding action.

Return value

Details

Corrective action

189

  • If the following values are output:

[LinkExpRBA] CategoryCode: 50

[LinkExpRBA] ErrorCode: 80

The network communication connection with the business server failed.

Check the following items:

  • The file transfer infrastructure may not have been set up on the business server. Ensure that the file transfer infrastructure has been set up.

  • The business server may have stopped. Ensure that the business server is running.

  • The file transfer infrastructure may not be running on the business server. Start the file transfer infrastructure.

    [Windows]

    Restart the Systemwalker File Transfer Library Control service.

    [Linux]

    Execute the following command:

    # service FJSVlnkbs start

  • An invalid IP address may have been specified in the "hosts" file for the business server name. Check the IP address specified in the "hosts" file.

  • If the remote server is a PC server with a TCP/IP connection, the number of connection requests on the business server may have exceeded the maximum number of requests that can be simultaneously processed by WinSock.

  • The connection may have been blocked by a firewall on the communication path.

  • If the business server is running Windows, the connection may have been blocked by security settings such as the Windows firewall.

If the situation does not change even after you have taken the appropriate action and then retried the processing, collect the investigation data by using swcfmg_collectinfo (problem investigation data collection command), and then contact Fujitsu technical support.

  • If the following values are output:

[LinkExpRBA] CategoryCode: 50

[LinkExpRBA] ErrorCode: 60

A timeout occurred during communication processing with the business server.

Possible causes are as follows:

  • The business server has stopped.

  • The business server has slowed down.

  • The communications environment is experiencing high load.

If the situation does not change even after you have taken the appropriate action and then retried the processing, collect the investigation data by using swcfmg_collectinfo (problem investigation data collection command), and then contact Fujitsu technical support.

If the cause of the problem is other than the above, contact Fujitsu technical support.

CFMGP20002 An error has occurred with file transfer processing. [Return value:{0}][Details:{1}]

Message Type

ERROR

Event Log

No

Description

An error has occurred with file transfer processing.

Parameter

{0}: Return value
{1}: Details

Corrective Action

If the return value and details that are output are as follows, take the corresponding action.

Return value

Details

Corrective action

161

  • If the following values are output:

None

File transfer has failed, as the file to transfer does not exist.

Check the following items:

When performing file collection of configuration modification, the collection files may not exist. Check that the collection files exist, and then perform the operation again.

177

  • If the following values are output:

destination file's parent directory does not exist

File transfer has failed, as the directory that is the transfer destination does not exist.

Check the following items:

When performing file distribution of configuration modification, the directory that is the distribution destination may not exist. Check that the directory of the distribution destination exists, and then perform the operation again.

  • If the following values are output:

  • sourcefile is specified none

File transfer has failed, as the file to transfer does not exist.

Check the following items:

When performing file collection of configuration modification, the collection files may not exist. Check that the collection files exist, and then perform the operation again.

187 or 189

  • If the following values are output:

[LinkExpRBA] CategoryCode: 40

[LinkExpRBA] ErrorCode : 10

or

[LinkExpRBA] CategoryCode: 40

[LinkExpRBA] ErrorCode: 30

As an error was detected while communicating with the business server, the process has stopped.

Check the following items:

  • When performing processing of file distribution or file collection of configuration modification, check the access privileges of the distribution and storage destination, and then perform the operation again.

  • When performing file distribution of configuration modification, the disk capacity of the distribution destination may be insufficient. Delete any unnecessary files, and then perform the operation again. When an operation is stopped, the distribution files may remain in the distribution destination. Manually delete them.

When performing file collection of configuration modification, the disk capacity of the storage destination may be insufficient. Delete any unnecessary files, and then perform the operation again. When an operation is stopped, the distribution files may remain in the storage location. Manually delete them.

  • If the following values are output:

[LinkExpRBA] CategoryCode: 50

[LinkExpRBA] ErrorCode: 80

The network communication connection with the business server failed.

Check the following items:

  • The file transfer infrastructure may not have been set up on the business server. Ensure that the file transfer infrastructure has been set up.

  • The business server may have stopped. Ensure that the business server is running.

  • The file transfer infrastructure may not be running on the business server. Start the file transfer infrastructure.

    [Windows]

    Restart the Systemwalker File Transfer Library Control service.

    [Linux]

    Execute the following command:

    # service FJSVlnkbs start

  • An invalid IP address may have been specified in the "hosts" file for the business server name. Check the IP address specified in the "hosts" file.

  • If the remote server is a PC server with a TCP/IP connection, the number of connection requests on the business server may have exceeded the maximum number of requests that can be simultaneously processed by WinSock.

  • The connection may have been blocked by a firewall on the communication path.

  • If the business server is running Windows, the connection may have been blocked by security settings such as the Windows firewall.

If the situation does not change even after you have taken the appropriate action and then retried the processing, collect the investigation data by using swcfmg_collectinfo (problem investigation data collection command), and then contact Fujitsu technical support.

  • If the following values are output:

[LinkExpRBA] CategoryCode: 50

[LinkExpRBA] ErrorCode: 60

A timeout occurred during communication processing with the business server.

Possible causes are as follows:

  • The business server has stopped.

  • The business server has slowed down.

  • The communications environment is experiencing high load.

If the situation does not change even after you have taken the appropriate action and then retried the processing, collect the investigation data by using swcfmg_collectinfo (problem investigation data collection command), and then contact Fujitsu technical support.

197

  • If the following values are output:

destination is invalid

or

filename is invalid

As there is an incorrect file name or file path for the transfer file, file transfer has failed.

Check the following items:

  • When the file involved is a pre-execution script or post-execution script, or scrip execution was attempted, check that the name of the specified script file is a character string of up to 155 characters, including alphanumeric characters, blank spaces, and the following symbols:

    ~, _, -, ., (, )

  • For file distribution of configuration modification, refer to "Definition of Setting Information" in the "Operator's Guide", and check that there are no errors in the directory path of the distribution destination.

  • For file collection of configuration modification, refer to "Definition of Setting Information" in the "Operator's Guide", and check that there are no errors in the file path of the collection file.

If the cause of the problem is other than the above, contact Fujitsu technical support.

CFMGP20003 An error has occurred with patch application processing. [Return value:{0}][Details:{1}][Execution result:{2}][Failed patch:{3}][Non-existent patch:{4}]

Message Type

ERROR

Event Log

No

Description

An error has occurred with patch application processing.

Parameter

{0}: Return value
{1}: Details
{2}: Execution result
{3}: Failed patch
{4}: Non-existent patch

Corrective Action

If the return value and details that are output are included in the following list, take the corresponding action.

Return value

Details

Corrective action

171

All

Application of one or more patches has failed.

Try again. If the problem is still not resolved, the patch cannot be applied.

172

All

The server needs to be restarted and application of patches has failed.

If the server needs to be restarted and has been set to reboot after application of patches, it will be restarted automatically. The problem is recorded as a log, but the server will be restarted and the processing to apply the patches that failed will be retried automatically.

If patch application still fails for a patch, try again. If the problem is still not resolved, the patch cannot be applied.

173

All

Execution of the yum command failed during the pre-application preparations.

Try again. If the problem is still not resolved, there may be an issue with the environment of the yum repository server. Check the status of the linkage server.

187 or 189

  • If the following values are output:

[LinkExpRBA] CategoryCode: 50

[LinkExpRBA] ErrorCode: 80

The network communication connection with the business server failed.

Check the following items:

  • The file transfer infrastructure may not have been set up on the business server. Ensure that the file transfer infrastructure has been set up.

  • The business server may have stopped. Ensure that the business server is running.

  • The file transfer infrastructure may not be running on the business server. Start the file transfer infrastructure.

    [Windows]

    Restart the Systemwalker File Transfer Library Control service.

    [Linux]

    Execute the following command:

    # service FJSVlnkbs start

  • An invalid IP address may have been specified in the "hosts" file for the business server name. Check the IP address specified in the "hosts" file.

  • If the remote server is a PC server with a TCP/IP connection, the number of connection requests on the business server may have exceeded the maximum number of requests that can be simultaneously processed by WinSock.

  • The connection may have been blocked by a firewall on the communication path.

  • If the business server is running Windows, the connection may have been blocked by security settings such as the Windows firewall.

If the situation does not change even after you have taken the appropriate action and then retried the processing, collect the investigation data by using swcfmg_collectinfo (problem investigation data collection command), and then contact Fujitsu technical support.

  • If the following values are output:

[LinkExpRBA] CategoryCode: 50

[LinkExpRBA] ErrorCode: 60

A timeout occurred during communication processing with the business server.

Possible causes are as follows:

  • The business server has stopped.

  • The business server has slowed down.

  • The communications environment is experiencing high load.

If the situation does not change even after you have taken the appropriate action and then retried the processing, collect the investigation data by using swcfmg_collectinfo (problem investigation data collection command), and then contact Fujitsu technical support.

Information about patches that failed to be applied is output in the displayed details, execution result, failed patch, or non-existent patch.

Item name

Meaning

Details

The error is output as a string.

The following examples show the output, including the output format, generated when application processing is performed for all the specified patches but the application of at least one patch fails. Refer to the Microsoft website for details on the "code" part of the error.

  • When a patch is applied to a Windows server

    Failed to install the update. detail="updateNumber(code),updateNumber(code)..."

    [Output example]

    Failed to install the update. detail="KB00001(0x8024402c),..."

    Note: Refer to "Application of Windows cumulative patches" below.

  • When a patch is applied to a Linux server

    Failed to install the update.
    detail="packageName(errorMessage),packageName(errorMessage)..."

    [Output example]

    Failed to install the update. detail="openssh.i386(Error: Missing Dependency:

    openssh.i386 >= 1.0 is needed by package openssh-askpass.i386 (Server)),..."

Execution result

The result of applying the patch is output.

The output format is as follows:

[RC(patchApplicationReturnCode)],[PatchNo(appliedPatchNumber)],[Message(message)]

Failed patches

If the process of applying patches fails or is interrupted, or the patches to be applied are not in the list of applicable patches, the following information will be output in CSV format. Information is output in the order specified by the option.

Patches to be output are included in non-existent patches.

  • Windows patches: Patch IDs

  • Linux patches: Package names

Non-existent patches

If the specified patch is not in the list of applicable patches returned by WSUS, the following information will be output in CSV format. Information is output in the order specified by the option.

  • Patch ID

Note

Application of Windows cumulative patches

Windows patches to be applied may have been absorbed into the latest patch (cumulative patch).

In this case, you must apply the latest cumulative patch containing the patches to be applied.

If the patch is not the latest patch, application may fail with the following message output as detailed information:

message:Failed to install the update. detail='updateNumber(code)'

execution_result:

RC,PatchNo,Message

4,patchNumber,"The specified update does not exist."

Apply the latest cumulative patch containing the patch that failed to be applied. Check the Microsoft website for information on the latest cumulative patch.

If you attempt to apply multiple patches and some fail to be applied for the above reason, ignore the failure.

CFMGP20004 Failed to set parameters. [Setting order:{0}][Software name:{1}][Version:{2}][Return value:{3}][Standard output:{4}][Standard error:{5}]

Message Type

ERROR

Event Log

No

Description

The processing to set parameters has failed.

Parameter

{0}: Setting order
{1}: Software name
{2}: Version
{3}: Return value of parameter setting script
{4}: Standard output of parameter setting script
{5}: Standard error of parameter setting script

Corrective Action

Take one of the following actions according to whether the name of the indicated software was pre-registered in this product or was registered using the software information management command.

  • If the software was pre-registered in this product

    Refer to the topic for the relevant software product in "Parameter Reference" in the Reference Guide, and take action accordingly.

  • If the software was registered using the software information management command

    Check the error information for the displayed return value, standard output, and standard error, and take action accordingly.

CFMGP20005 An error has occurred during parameter setting.

Message Type

ERROR

Event Log

No

Description

An error has occurred during parameter setting.

Corrective Action

Check the logs on the server for which the parameters are being set, and take action accordingly.

If the problem is still not resolved, contact Fujitsu technical support.

CFMGP20006 Failed to execute the script. [Return value:{0}][Standard output:{1}][Standard error:{2}]

Message Type

ERROR

Event Log

No

Description

Execution of the script has failed.

Parameter

{0}: Return value of script
{1}: Standard output of script
{2}: Standard error of script

Corrective Action

Check the error information for the displayed return value, standard output, and standard error, and take action accordingly.

CFMGP20007 An error has occurred during OS restart. [Return value:{0}][Details:{1}]

Message Type

ERROR

Event Log

No

Description

An error has occurred while the operating system was restarting.

Parameter

{0}: Return value
{1}: Details

Corrective Action

If the return value and details that are output are included in the following list, take the corresponding action.

Return value

Details

Corrective action

187 or 189

  • If the following values are output:

[LinkExpRBA] CategoryCode: 50

[LinkExpRBA] ErrorCode: 80

The network communication connection with the business server failed.

Check the following items:

  • The file transfer infrastructure may not have been set up on the business server. Ensure that the file transfer infrastructure has been set up.

  • The business server may have stopped. Ensure that the business server is running.

  • The file transfer infrastructure may not be running on the business server. Start the file transfer infrastructure.

    [Windows]

    Restart the Systemwalker File Transfer Library Control service.

    [Linux]

    Execute the following command:

    # service FJSVlnkbs start

  • An invalid IP address may have been specified in the "hosts" file for the business server name. Check the IP address specified in the "hosts" file.

  • If the remote server is a PC server with a TCP/IP connection, the number of connection requests on the business server may have exceeded the maximum number of requests that can be simultaneously processed by WinSock.

  • The connection may have been blocked by a firewall on the communication path.

  • If the business server is running Windows, the connection may have been blocked by security settings such as the Windows firewall.

If the situation does not change even after you have taken the appropriate action and then retried the processing, collect the investigation data by using swcfmg_collectinfo (problem investigation data collection command), and then contact Fujitsu technical support.

  • If the following values are output:

[LinkExpRBA] CategoryCode: 50

[LinkExpRBA] ErrorCode: 60

A timeout occurred during communication processing with the business server.

Possible causes are as follows:

  • The business server has stopped.

  • The business server has slowed down.

  • The communications environment is experiencing high load.

If the situation does not change even after you have taken the appropriate action and then retried the processing, collect the investigation data by using swcfmg_collectinfo (problem investigation data collection command), and then contact Fujitsu technical support.

If the cause of the problem is other than the above, contact Fujitsu technical support.

CFMGP20008 An error has occurred during command execution. [Return value:{0}][Command:{1}][Details:{2}]

Message Type

ERROR

Event Log

No

Description

An error has occurred during command execution.

Parameter

{0}: Return value
{1}: Command
{2}: Details

Corrective Action

If the return value and details that are output are included in the following list, take the corresponding action.

Return value

Details

Corrective action

187 or 189

  • If the following values are output:

[LinkExpRBA] CategoryCode: 50

[LinkExpRBA] ErrorCode: 80

The network communication connection with the business server failed.

Check the following items:

  • The file transfer infrastructure may not have been set up on the business server. Ensure that the file transfer infrastructure has been set up.

  • The business server may have stopped. Ensure that the business server is running.

  • The file transfer infrastructure may not be running on the business server. Start the file transfer infrastructure.

    [Windows]

    Restart the Systemwalker File Transfer Library Control service.

    [Linux]

    Execute the following command:

    # service FJSVlnkbs start

  • An invalid IP address may have been specified in the "hosts" file for the business server name. Check the IP address specified in the "hosts" file.

  • If the remote server is a PC server with a TCP/IP connection, the number of connection requests on the business server may have exceeded the maximum number of requests that can be simultaneously processed by WinSock.

  • The connection may have been blocked by a firewall on the communication path.

  • If the business server is running Windows, the connection may have been blocked by security settings such as the Windows firewall.

If the situation does not change even after you have taken the appropriate action and then retried the processing, collect the investigation data by using swcfmg_collectinfo (problem investigation data collection command), and then contact Fujitsu technical support.

  • If the following values are output:

[LinkExpRBA] CategoryCode: 50

[LinkExpRBA] ErrorCode: 60

A timeout occurred during communication processing with the business server.

Possible causes are as follows:

  • The business server has stopped.

  • The business server has slowed down.

  • The communications environment is experiencing high load.

If the situation does not change even after you have taken the appropriate action and then retried the processing, collect the investigation data by using swcfmg_collectinfo (problem investigation data collection command), and then contact Fujitsu technical support.

If the cause of the problem is other than the above, contact Fujitsu technical support.

CFMGP20009 An error has occurred during processing. [Component name:{0}][Return value:{1}][Details:{2}]

Message Type

ERROR

Event Log

No

Description

An error has occurred during processing.

Parameter

{0}: Component name
{1}: Return value
{2}: Details

Corrective Action

If the return value and details that are output are included in the following list, take the corresponding action.

Return value

Details

Corrective action

187 or 189

  • If the following values are output:

[LinkExpRBA] CategoryCode: 50

[LinkExpRBA] ErrorCode: 80

The network communication connection with the business server failed.

Check the following items:

  • The file transfer infrastructure may not have been set up on the business server. Ensure that the file transfer infrastructure has been set up.

  • The business server may have stopped. Ensure that the business server is running.

  • The file transfer infrastructure may not be running on the business server. Start the file transfer infrastructure.

    [Windows]

    Restart the Systemwalker File Transfer Library Control service.

    [Linux]

    Execute the following command:

    # service FJSVlnkbs start

  • An invalid IP address may have been specified in the "hosts" file for the business server name. Check the IP address specified in the "hosts" file.

  • If the remote server is a PC server with a TCP/IP connection, the number of connection requests on the business server may have exceeded the maximum number of requests that can be simultaneously processed by WinSock.

  • The connection may have been blocked by a firewall on the communication path.

  • If the business server is running Windows, the connection may have been blocked by security settings such as the Windows firewall.

If the situation does not change even after you have taken the appropriate action and then retried the processing, collect the investigation data by using swcfmg_collectinfo (problem investigation data collection command), and then contact Fujitsu technical support.

  • If the following values are output:

[LinkExpRBA] CategoryCode: 50

[LinkExpRBA] ErrorCode: 60

A timeout occurred during communication processing with the business server.

Possible causes are as follows:

  • The business server has stopped.

  • The business server has slowed down.

  • The communications environment is experiencing high load.

If the situation does not change even after you have taken the appropriate action and then retried the processing, collect the investigation data by using swcfmg_collectinfo (problem investigation data collection command), and then contact Fujitsu technical support.

If the cause of the problem is other than the above, contact Fujitsu technical support.

CFMGP20010 An unexpected error has occurred during processing.

Message Type

ERROR

Event Log

No

Description

An unexpected error has occurred during processing.

Corrective Action

When the file involved is a pre-execution script or post-execution script, or scrip execution was attempted, check that the name of the specified script file is a character string of up to 155 characters, including alphanumeric characters, blank spaces, and the following symbols:

~, _, -, ., (, )

If the cause of the problem is something other than the above, contact Fujitsu technical support.

CFMGP20011 Processing was terminated. [Return value:{0}][Details:{1}]

Message Type

ERROR

Event Log

No

Description

The processing was terminated.

Parameter

{0}: Return value
{1}: Details

Corrective Action

A timeout may have occurred during processing. Take one of the following actions:

  • If the script was executed before a script or command was executed, script and command processing may have entered the standby mode due to interactive processing, and may not have been completed. Refer to "Creating Scripts and Specifying Commands" in the Operation Guide, review the script and the command, and request processing again.

  • A timeout may have occurred during communication processing with the business server. Possible causes are listed below. Check each possible cause, and then request processing again.

    • The business server has stopped.

    • The business server has slowed down.

    • The communication environment is experiencing high load.

  • If the cause of the problem is other than the above, contact Fujitsu technical support.

CFMGP20012 The command execution process has failed. [Return value:{0}][Standard output:{1}][Standard error:{2}]

Message Type

ERROR

Event Log

No

Description

Execution of the command has failed.

Parameter

{0}: Return value of the command
{1}: Standard output of the command
{2}: Standard error of script

Corrective Action

Check the error information for the displayed return value, standard output, and standard error, and take action accordingly.

CFMGP20013 Creation of the directory on the admin server has failed. [Directory path={0}][Return value:{1}][Details:{2}]

Message Type

ERROR

Event Log

No

Description

Creation of a directory on the admin server has failed.

Parameter

{0}: Directory path
{1}: Return value
{2}: Details

Corrective Action

Check the access privileges for the displayed directory.

CFMGP20014 Failed to receive the assets. [Details:{0}]

Message Type

ERROR

Event Log

No

Description

Acquisition of the asset has failed.

Parameter

{0}: Details

Corrective Action

Check the disk capacity of the admin server. If there is not enough free space, delete any unnecessary files and then execute the command again.

If the problem persists, contact Fujitsu technical support.

CFMGP20015 The process for preparing switchover to single-user mode has failed. [Return value:{0}]

Message Type

ERROR

Event Log

No

Description

The process for preparing switchover to single-user mode has failed.

Parameter

{0}: Return value

Corrective Action

  • When the return value is 249 or 250, check whether the FJSVsglcf service has been registered already. If the FJSVsglcf service is already registered, delete it and then try the operation again.

  • When the return value is 242, the inittab_FJSVsglcf file that was backed up for a job that was executed before may remain without being restored. In that case, execute the following command to restore the inittab_FJSVsglcf file that was backed up, and then try the operation again.

    mv -f /etc/inittab_FJSVsglcf /etc/inittab

If the problem persists, contact Fujitsu technical support.

CFMGP20016 Timeout has occurred during switchover from single-user mode.

Message Type

ERROR

Event Log

No

Description

Switchover from single-user mode has failed.

Corrective Action

After a script or command was executed, timeout has occurred during switchover from single-user mode. The following problems may have occurred:

  • The specified script or command has not been completed within one hour due to a hang-up or a similar reason.

  • After the specified script or command was executed, an error occurred when switching over from single-user mode.

Recover the environment using the following procedure:

  1. Restarting the target server switches it over from single-user mode.

  2. Access the target server and confirm the execution results of the specified script or command. Standard output, standard errors, and return values are output to the following log on the target server:

    /var/opt/FJSVcfmgb/logs/swcfmga_configuration_log

  3. When the target server is operating using single-user mode, restore the inittab file or the backed up default.target file using the following command:

    • For Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6

      mv -f /etc/inittab_FJSVsglcf /etc/inittab

    • For Red Hat Enterprise Linux 7

      mv -f /etc/default.target_FJSVsglcf /etc/systemd/system/default.target

  4. When the target server is operating in single-user mode, restart the target server and switch it from single-user mode back to the previous mode.

  5. Retry, cancel, or continue the job using the execution results confirmed in step 2.

CFMGP20017 Acquisition of the results of script execution or command execution has failed. [Return value:{0}][Details:{1}]

Message Type

ERROR

Event Log

No

Description

Acquisition of the results of script execution or command execution has failed.

Corrective Action

A script or a command was executed but acquisition of the results failed.

Access the target server and confirm the execution results of the specified script or command. Standard output, standard errors, and return values are output to the following log on the target server:

/var/opt/FJSVcfmgb/logs/swcfmga_configuration_log

Check the log and if the script or command has ended normally, continue the job. If an error has occurred, retry or cancel the job.

PreviousNext
Copyright 2010-2016 FUJITSU LIMITED