GAUSS-53500 -- GAUSS-53599

GAUSS-53500: "Failed to connect to %s."

SQLSTATE: None

Description: Failed to connect to the host.

Solution: Check the network connection.

GAUSS-53501: "Undefined action.""Connection timeout."

SQLSTATE: None

Description: The network connection fails or the function execution times out.

Solution: Check the network connection and available storage space.

GAUSS-53502: "Connection timeout.""Failed to parde host IP from %s."

SQLSTATE: None

Description: The operation is invalid.

Solution: Check the parameters in the script.

GAUSS-53503: "Failed to parde host IP from %s."

SQLSTATE: None

Description: Failed to read the IP address list.

Solution: Check the format of the input IP address list or the IP address list file.

GAUSS-53504: "Bad response %s."

SQLSTATE: None

Description: The command output is not as expected.

Solution: Check the script execution environment.

GAUSS-53505: "Installation directory does not exist, please check whether the installation is OK."

SQLSTATE: None

Description: The GDS installation directory is not found.

Solution: Check whether GDS has been uninstalled or the environment variables of the user are damaged.

GAUSS-53506: "Failed to check whether a process on this port exists with exception: %s."

SQLSTATE: None

Description: The GDS process is not found on the specified port.

Solution: Ensure that the port number is correct and the process is not ended.

GAUSS-53507: "OS environments not set, please check install log."

SQLSTATE: None

Description: The GDS installation information is not found in the environment variables.

Solution: Ensure that GDS has been properly installed.

GAUSS-53508: "Failed to add watch dog for %s."

SQLSTATE: None

Description: Failed to create a crontab.

Solution: Ensure that you have the permission to write to the crontab file.

GAUSS-53509: "Failed to delete watch dog for %s."

SQLSTATE: None

Description: Failed to delete a crontab.

Solution: Ensure that you have the permission to write to the crontab file.

GAUSS-53510: "Failed to save start command for %s."

SQLSTATE: None

Description: Failed to save the GDS startup command to the file.

Solution: Ensure that the disk is not full and you have the permission to read and write to the file.

GAUSS-53511: "Failed to get start command for %s."

SQLSTATE: None

Description: Failed to obtain the GDS startup command from the file.

Solution: Ensure that the file exists and you have the permission to read the file.

GAUSS-53512: "Retry to dispatch package 3 times, with error: %s."

SQLSTATE: None

Description: Failed to distribute the package to nodes during GDS installation.

Solution: Check the network connection, permission on the specified directory on each node, and available disk space on each node.

GAUSS-53513: "Failed to load environment parameters."

SQLSTATE: None

Description: Failed to load the environment variables.

Solution: Check the execute permission.

GAUSS-53514: "Unclassified exceptions: %s."

SQLSTATE: None

Description: The exception information is not classified.

Solution: Rectify the fault based on the captured exception information.

GAUSS-53515: "Cannot read check result. Please try again."

SQLSTATE: None

Description: Failed to read the environment variable check result during GDS installation.

Solution: Ensure that the environment variables are normal and try again.

GAUSS-53516: "Check result shows unqualified items. Installation stop."

SQLSTATE: None

Description: During GDS installation, the environment variable check result shows that some environment variables are not as expected.

Solution: Run the gds_check -t fix command and check the network connection.

GAUSS-53517: "The user %s does not have the permission to access the directory %s."

SQLSTATE: None

Description: The user does not have the permission to read and write to the directory.

Solution: Check the permission on directory or change the installation directory.

GAUSS-53518: "Dispatch package failed, with error: %s."

SQLSTATE: None

Description: Failed to distribute the package to nodes during GDS installation.

Solution: Check the permission on the specified directory, available disk space, and whether the specified installation directory is empty.