Troubleshooting O&M Project Deployment Exceptions

Application Scenario

This document briefly describes the causes and solutions of abnormal project deployment/connection in FineOps.

Error: The current server limit minimum number of cpu cores is 8

Issue Description

During node configuration, an error message appears stating "The current server limit minimum number of cpu cores is 8," as shown in the following figure.

Cause Analysis

During new project deployment, FineOps will perform a system configuration check on the server and report an error if the requirements are not met.

The configuration requirements vary with the application type and the node type. Refer to the prompts during deployment for details.

Solution

Increase the server specifications and then proceed with project deployment.

Note that meeting these configuration requirements only ensures that nodes can be successfully added. It does not guarantee successful deployment. The system will perform additional environment checks based on the components to be deployed.

Therefore, you are advised to prepare servers that meet all requirements based on the server preparation document.

Error: Server IP try to bind ports 9114,9100,9200,9080,9070 failed!

Issue Description

During project deployment, an error is reported, stating "Server IP try to bind ports 9114,9100,9200,9080,9070 failed!"

Cause Analysis

1. These ports on the project server are occupied.

2. These ports on the project server are not accessible over the intranet from the FineOps server.

Solution

1. Check whether the default mapped ports are already in use, and confirm that the project server and the FineOps server can communicate over the intranet.

For instructions on port occupancy inspection and firewall configuration, see Port Occupancy Inspection and Firewall Configuration.

2. If any of these ports are already in use, prepare other available ports.

Click the Custom Deployment button in the Deployment List step, and modify the relevant ports.

Automatic Information Population During Redeployment Upon Deployment Failure

This function is available from FineOps V1.9.0.

If the last project deployment in FineOps failed, when you attempt to deploy a new project, a prompt will appear: "Detected a project that failed to be deployed last time. Continue the deployment?"

The system will automatically populate the project settings and node configuration from the last deployment attempt after you click Continue, saving time.

Error: Failed to write file /home/backup/config/default.zip

Issue Description

When you deploy a cluster project using a self-prepared file server, an error occurs: "Failed to write file /home/backup/config/default.zip Exception message: No such file."

Cause Analysis

The user account prepared for connecting to the file server does not have the read and write permission on the corresponding directory.

Solution

You are advised to use the root user.

If you can only use a regular user, assign the read and write permission to that user according to the file path in the error message. FanRuan does not provide guidance on this step.

Error: xfs format is required

Issue Description

When you deploy the MinIO component via FineOps when deploying a FineBI 6.1 project, an error occurs: "The driver format of the [/root/data] of the minio deployment node 192.168.1.34 is [ext4], and xfs format is required."

Cause Analysis

If you use the FineOps-deployed MinIO component for data storage, the disk format must be XFS.

A non-XFS disk might result in data write failure even with available disk space.

Solution

Adjust the disk format of the server intended for deploying the data storage component to XFS.

This operation may involve disk formatting. FanRuan does not provide related guidance. Proceed cautiously under the guidance of your server vendor.

Error: Do not use system directories as dataroot

Issue Description

An error occurs during node configuration: "Do not use system directories as dataroot!"

Cause Analysis

The directories/paths /, /usr, /root, and /usr/local are system directories/paths.

They cannot be used as the mounting path in the node configuration.

Solution

Use a different path, or create a folder in these paths to serve as the mounting path of FineOps.

Error: No more authentication methods available

Issue Description

During new project deployment, an error occurs: "No more authentication methods available."

Cause One: Incorrect Password

If this error appears during the Node Configuration step, check if the password of the provided server user is correct.

If you set Verification Method to Public Key, upload a private key file with a .key extension, for example, id_rsa.key.

Do not upload private key files with other extensions. Do not upload public key files, for example, id_rsa.pub.

Cause Two: SSH Not Supported

Ensure that the FineOps server enables logins to the target project server via SSH.

Modify the sshd_config file (/etc/ssh/sshd_config) on the server to meet the SSH connection requirements.

Error: The component bi-web has not started successfully after 10 minutes

Issue Description

An error occurs during new project deployment: "The component bi-web has not started successfully after 10 minutes."

Cause One: Incorrect Encoding of the External Configuration Database

The self-provided external configuration database does not support the utf8mb4 encoding.

Solution

1. You are advised to use a new FineOps-deployed database as the external database.

2. If you must use a self-provided MySQL database as the configuration database, ensure that the default character set is utf8mb3 and the default collation is utf8mb3_bin.

Cause Two: Project Component Startup Timeout

The default startup timeout for each component is 10 minutes during new project deployment. The component deployment will be considered to have failed if this duration is exceeded.

Solution 

Increase the Startup Timeout value under Setting > Timeout Check in FineOps, click Save, and then retry the deployment.