Overview
Version
FineBI Version | Version Change |
6.0 | / |
Concept Introduction
Cluster: A cluster is a technology that connects multiple systems together, allowing multiple servers to work like one machine (or appear to be one machine).
Dual-machine hot standby: Dual-machine hot standby refers to the hot standby (or high availability) of two servers in a high availability system.
Multi-server system: You can directly install the system you have developed and deploy for multiple users (with the same system). Or multi-server system can automatically move apps in the current machine (if it has a problem) to the two backup machines (three machines in total).
Registration Method
Registration Method | Introduction | Help 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 email a screenshot of the version information page to the business personnel. 2. Ensure that the logged-in node can communicate with all nodes. (If not, all node information cannot be exported with a single operation .) | |
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 no less than 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 no less than the number of nodes. | |
Local Container Authentication | Support The maximum registration number needs to be no less than 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). | |
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 no less than the number of nodes. | Container Private Cloud Authentication |
Encryption Lock Authentication | Not support | / |
Failed Registration
If registration fails, a prompt window pops up.
Reasons for Local Information Authentication Failures
Overall FailureCause | Specific Information |
Expired certificate | Expired Time: 2019/02/22 |
Mismatched version matched | Certified Application Version: 9.0 Local Application Version: 10.0 |
Node of Registration Failed | Cause | Specific Information |
node-47-1 | Mismatched MAC address | Authentication MAC address: Address Local MAC address: Address |
node-47-1 | Mismatched machine code | Authentication machine code: Code Local machine code: Code |
node-47-1 | Mismatched application name | Authentication application name: Application name Local application name: Application name |
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 | Mismatched project content | Authentication project content: Content Local project content: Content |
Reasons for Private Cloud Authentication Failures
Overall FailureCause |
Incorrect data format |
Mismatched Version |
Expired certificate |
The authorization server has been uninstalled, please reapply. |
Node of Failed Registration | Cause |
node-47-1 | The maximum number of authorizations has been reached. |
node-47-1 | 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 a machine.) |
Cause |
Incorrect data format |
Incorrect parameter |
Unauthorized account and password |
Mismatched version |
Abnormal account status |
Expired certificate |
Node of Falied Registration | Cause |
node-47-1 | Error occurs when you insert data into REDIS database. |
node-47-1 | 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 a machine.). |
Note:Notes
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 not matched. Mac address not matched. | Authentication machine code: Code Local machine code: Code Authentication MAC address: Address Local MAC address: Address |
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):
Certificate expired
Expired Time: 2019/02/22
