Version
Report Server Version | Version Update |
11.0 | / |
Introduction
Cluster: a technology that connects multiple systems together, allowing multiple servers to work like one machine (or appear to be one machine).
Dual server hot standby: hot standby (or high availability) of two servers in a high availability system, which is commonly used in China.
Multi-server system: Directly install the system you have developed to deploy for multiple users with the same system or automatically move apps in the current machine (if it has a problem) to the other two backup machines (three machines in total). Or automatically move apps in the current machine (if it has a problem) to the two backup machines (three machines in total).
Registration Methods
Registration Methods | Description | Document |
Local Machine Information Authentication | Support Export all nodes' registration information of the rif file with one click under any node in the cluster environment. One cluster corresponds to one lic file. You just need to upload the lic file once on one node to register successfully. Registration fees are charged according to the number of cluster nodes.  Note:1. If exporting registration information is failed, you can send a screenshot of the version information page to the business personnel through email. 2. Ensure that the logged-in node can communicate with all nodes. (If not, all node information cannot be exported at once.) | |
Private Cloud Authentication | Support Authorize for multiple nodes through one authorization server. All nodes and authorization servers must be able to access each other. The number of authorizations under the authorization server needs to be greater than or equal to the number of nodes. | |
Public Cloud Authentication | Support All nodes need to be able to access the FanRuan public cloud authentication server. The maximum registration number needs to be greater than or equal to the number of nodes. | |
Local Container Authentication | Support The maximum registration number needs to be greater than or equal to the number of nodes. Before you register the cluster project, ensure that the time of each server is consistent. If all nodes in the cluster are restarted, the report project needs to be re-authenticated (rescan the QR code and enter the verification code without re-uploading the Cotainer.lic file). You are not required to re-upload the Container.lic file, just re-scan the QR code and enter the verification code. | |
Container Private Cloud Authentication | Support All nodes and authorization servers must be able to access each other. The number of authorizations under the authorization server needs to be greater than or equal to the number of nodes. | |
Encryption Lock Authentication | Not support | / |
Failed Registration
If registration fails, a prompt window pops up.
Click Back to view the reason for registration failure and troubleshoot the problem based on the specific failure reason, as shown in the following figure.
Reasons for Local Information Authentication Failures
Overall Failure
Cause | Specific Information |
Expired Certificate | Expiration Date: 2019/02/22 |
Version Mismatch | Certified Application Version: 9.0 Local Application Version: 10.0 |
Node Failure
Node of Registration Failed | Cause | Specific Information |
node-47-1 | MAC Address Mismatch | Authentication MAC Address: xxx Local MAC Address: xxx |
node-47-1 | Machine Code Mismatch | Authentication Machine Code: xxx Local Machine Code: xxx |
node-47-1 | Application Name Mismatch | Authentication Application Name: xxx Local Application Name: xxx |
node-47-1 | The maximum number of authorizations has been reached. | The certificate has been used by other projects on the same server. |
node-47-1 | Project Content Mismatch | Authentication Project Content: xxx Local Project Content: xxx |
Reasons for Private Cloud Authentication Failure
Overall Failure
Cause |
Incorrect Data Format |
Version Mismatch |
Expired Certificate |
The authorization server has been uninstalled, please reapply. |
Node Failure
Node of Registration Failed | Cause |
node-47-1 | The maximum number of authorizations has been reached. |
node-47-1 | The IP address is not within the allowed range. |
node-47-1 | The domain name is not within the allowed range. |
node-47-1 | The app name is not within the allowed range. |
node-47-1 | This machine is not authorized and does not need to be unbound. (The prompt occurs when you unbind an unauthorized machine.). |
Reasons for Public Cloud Authentication Failure
Overall Failure
Cause |
Incorrect Data Format |
Incorrect Parameter |
Unauthorized Account and Password |
Version Mismatch |
Abnormal Account Status |
Expired Certificate |
Node Failure
Node of Registration Failed | Cause |
node-47-1 | Error occurs when you insert data into the REDIS database. |
node-47-1 | The IP address is not within the allowed range. |
node-47-1 | The domain name is not within the allowed range. |
node-47-1 | The app name is not within the allowed range. |
node-47-1 | Error occurs when you update MySQL database. |
node-47-1 | The maximum number of authorizations has been reached. |
node-47-1 | This machine is not authorized and does not need to be unbound. (The prompt occurs when you unbind an unauthorized machine.). |
Note:Other Description
1. All causes for failure (if have) of a single node will be displayed in the platform.
For example, both machine codes and Mac address are not matched.
node-47-1 | Machine code is not matched. Mac address is not matched. | Authentication Machine Code: xxx Local Machine Code: xxx Authentication MAC Address: xxx Local MAC Address: xxx |
2. Only causes of overall registration failures are displayed when there are both causes of overall registration failures and causes of single node failures.
For example, the certificate is expired and the machine code of the node-47-1 is not matched. Only the certificate expiration is prompted (no prompt for mismatched machine code):
Expired Certificate
Expiration Date: 2019/02/22
Previous：Plugin Registration
