Top
ServerView Resource Orchestrator V3.1.0 Messages
ServerView

3.2.1 425XX Series

This section explains the 425XX message series.

42501

FJSVrcx:WARNING:42501:invalid value in the configuration file (file=file, detail=detail)

[Virtual Edition]

Description

There is an invalid value in the definition file.

The file name is displayed for file.

The details of the error are displayed for detail. When multiple errors are detected, they are displayed separated by commas (",").

  • When file is "product_report.rcxprop", and detail is "product_report " or "product_report_for_cli"

    Values for output format have not been set correctly.

Corrective Action

  • When the file name is "product_report.rcxprop"

    Check the value corresponding to the key value displayed for detail, and change the setting to the correct value, which is case sensitive.

    For details, refer to "F.1.2 Configuring Display of Errors that Occur on Related Products" in the "Setup Guide VE".


[Cloud Edition]

Description

There is an invalid value in the definition file.

The file name is displayed for file.
The details of the error are displayed for detail. When multiple errors are detected, they are displayed separated by commas (",").

  • When "l_server.rcxprop" is displayed for "file", and "allocate_after_create" or "auto_preserved" is displayed for detail

    The value in the [Create an L-Server] dialog or the [Modify an L-Server] dialog has not been correctly set. Therefore, an unintended value may be set.

  • When "vnetwork_ibp.rcxprop" is displayed for file, and "support_ibp_mode" is displayed for detail

    The IBP setting values have not been set correctly.

  • When file is "product_report.rcxprop", and detail is "product_report " or "product_report_for_cli"

    Values for output format have not been set correctly.

Corrective Action

  • When the file name is "vnetwork_ibp.rcxprop"

    Check the value corresponding to the key value displayed for detail, and change the setting to the correct value, which is case sensitive. After that, take corrective action based on the content of detail.

    • "allocate_after_create"

      • When there is no problem with the L-Server even if resources are allocated

        No action is necessary.

      • When only an L-Server definition has been created

        After deleting the L-Server, perform creation again.

    • "auto_preserved"

      • When resources have been allocated to the L-Server

        Change the "Resource release" in the [Modify an L-Server] dialog.

      • When an L-Server has only been defined

        Change the "Resource release" in the [Modify L-Server's definition] dialog.

        When changing the L-Server using the command, set the Repurpose element, and then change the L-Server.

    For details, refer to "17.8.1 Installation" in the "User's Guide for Infrastructure Administrators(Resource Management) CE".

  • When the file name is "vnetwork_ibp.rcxprop"

    Check the value corresponding to the key value displayed for detail, and change the setting to the correct value, which is case sensitive.

    For details, refer to "D.4 Network Preparations" in the "Design Guide CE".

  • When the file name is "product_report.rcxprop"

    Check the value corresponding to the key value displayed for detail, and change the setting to the correct value, which is case sensitive.

    For details, refer to "G.1.4 Configuring Display of Errors that Occur on Related Products" in the "Setup Guide CE".


42502

FJSVrcx:WARNING:42502: failed to read the configuration file (file=file)

[Cloud Edition]

Description

Failed to read the definition file.
The file name is displayed for file.

Corrective Action

Check the following, resolve the cause of the error and then re-execute.

  • The file does not exist

  • Access privileges of the file and directory

  • The file is locked by another program


42503

FJSVrcx:WARNING:42503:control of obj failed. perform recovery referring to the message msg.

[Cloud Edition]

Description

When separating disk resources from the virtual storage, an error occurred in the storage management software, but the separation of the disk resources was successful.

However, action regarding the storage machine identification number must be taken.

In obj, the resource name of the storage management software is displayed.

The message output by the storage management product is output to msg.

Corrective Action

Check the message displayed in msg, then refer to the manual for the storage management product and take the required action.


42504

FJSVrcx:WARNING:42504:obj:type initialization failed

[Cloud Edition]

Description

The initialization of the content of the resource displayed in type failed.

  • When type is "disk"

    The disk resource name is displayed in obj.

    The initialization of the content of the disk resource failed. However, the process that was running is still being executed.

Corrective Action

  • When type is "disk"

    Please execute the following procedures when the VM host of RHEL-KVM that can be accessed obj has stopped.

    • Release the registration of the disk resource of obj

    • Start the VM host of RHEL-KVM

    • Log in to the VM host of RHEL-KVM

    • Execute the initialization command of content of the raw device or disk partition corresponding to obj in the VM host of RHEL-KVM

    • Re-registration of the disk resource of obj

    Please release the registration of the disk resource of obj when neither the raw device nor the disk partition corresponding to obj exist.


42505

FJSVrcx:WARNING:42505:obj:ip:path:not set as a mount point

Description

The mount point of the path path to the disk resource obj on the VM host ip has not been configured.
Even if this message is output, creation of a VM guest is continued.

A VM guest is created on the disk which the directory of path is deployed on. Therefore, migration of the VM guest between servers is not available.

Corrective Action

Check that there are no errors in the mount settings for path on the VM host ip.
When there are errors in the mount settings, stop the L-Server, correct the mount settings, and then migrate the file under path to the mounted volume.


42540

FJSVrcx:WARNING:42540:failed to write records. detail=detail

[Cloud Edition]

Description

The recording process of the operation log failed.

Corrective Action

  • When detail is "filesystem full"

    Check the system log, resolve the cause of the error, and then perform the operation again.

    • Check if there are any error messages regarding the disk or file system.

    • Check if there is a quota limit or file system full message.