faqs - 帮助中心首页-华为云 · 2020. 11. 11. · follow the instructions in the next...

Blockchain Service

FAQs

Issue 01

Date 2021-04-26

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2021. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without priorwritten consent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respectiveholders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei andthe customer. All or part of the products, services and features described in this document may not bewithin the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,information, and recommendations in this document are provided "AS IS" without warranties, guaranteesor representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Issue 01 (2021-04-26) Copyright © Huawei Technologies Co., Ltd. i

Contents

1 Service Usage............................................................................................................................11.1 What Is Data Aging on Orderers and How Do I Enable It?......................................................................................11.2 How Do I Clear Residual Log Files After a BCS Service Is Deleted?...................................................................... 21.3 What Can I Do If the Marbles Game Fails to Be Installed in the Walkthrough?..............................................21.4 How Many Quotas Do I Have for the BCS?................................................................................................................... 31.5 How Can I Enable Automatic Backup and Restore Data of an SFS Turbo File System?................................ 41.6 How Do I Check Whether the ICAgent Is Installed for the Cluster?......................................................................51.7 How Do I Enable the IPv6 EIP Function?........................................................................................................................ 61.8 How Do I Upgrade a BCS Service from Fabric v1.1.0 to Fabric v1.4.0?................................................................ 71.9 What Can I Do If I Can't Open the Blockchain Management Console?............................................................ 101.10 What Should I Do If My BCS Service Remains in the Creating State?.............................................................101.11 What Should I Do If a Peer Restarts Frequently with the Error Message "PanicDB not exist"?.............101.12 What Can I Do If the Block Height Is Inconsistent Between Peers Due to Gossip Exceptions?..............111.13 What Can I Do If the CPU Usage of a Blockchain Node Reaches 100%?...................................................... 111.14 Why Can't I Log In to the Blockchain Management Console?........................................................................... 111.15 How Do I Reset the Management Password?.......................................................................................................... 131.16 BCS.4009100: System Error............................................................................................................................................. 141.17 How Do I Change the Name of a BCS Service?.......................................................................................................141.18 How Do I Resolve a Reference Conflict During Chaincode Installation for a BCS Service of Fabricv1.4?.................................................................................................................................................................................................. 151.19 Why Is "TLS handshake failed" Repeatedly Displayed in the Service Log?....................................................161.20 How Do I View Chaincode Logs If My BCS Service Uses Fabric v2.0?............................................................. 17

2 Consultation........................................................................................................................... 182.1 What Is Blockchain?............................................................................................................................................................. 182.2 What Benefits Can Blockchain Bring?............................................................................................................................192.3 How Do I Determine Whether a Blockchain Is Necessary?................................................................................... 192.4 What Underlying Framework Is Used for HUAWEI CLOUD BCS?........................................................................192.5 What Consensus Mechanisms Does HUAWEI CLOUD BCS Support?.................................................................202.6 What Are the BCS Deployment Specifications?..........................................................................................................202.7 How Do I Update a Chaincode If It Contains Bugs?.................................................................................................202.8 Can All Blocks Be Saved As More and More Blocks Are Created?.......................................................................202.9 Can BCS Services Deployed on the Public Cloud Access Blockchain Nodes on Other Clouds?................. 212.10 What Competitive Advantages Does HUAWEI CLOUD BCS Have?.................................................................. 21

Blockchain ServiceFAQs Contents

Issue 01 (2021-04-26) Copyright © Huawei Technologies Co., Ltd. ii

2.11 In Which Direction and What Capabilities Will HUAWEI CLOUD BCS Develop?......................................... 212.12 What Are the Specifications of VMs to Be Purchased for BCS?......................................................................... 212.13 How Do I Get Access to the Partners of HUAWEI CLOUD BCS for More Services?....................................222.14 When Do I Need to Hibernate or Wake a Service?................................................................................................ 222.15 What Ledger Storage Modes Are Supported?.......................................................................................................... 222.16 What Are the Differences Between Channel Isolation and Privacy Protection?.......................................... 232.17 Can I Invite Individual Users to Join a Consortium?...............................................................................................232.18 How Is the Performance of BCS?.................................................................................................................................. 23

3 Purchases and Deployment.................................................................................................243.1 What Can I Do If I Fail to Purchase a BCS Service?.................................................................................................. 243.1.1 General Checks................................................................................................................................................................... 243.1.2 Detailed Checks..................................................................................................................................................................263.1.2.1 CCE Cluster Quota Used Up....................................................................................................................................... 263.1.2.2 Failed to Create a Cluster............................................................................................................................................263.1.2.3 Failed to Create a PVC..................................................................................................................................................273.1.2.4 Cluster Already In Use.................................................................................................................................................. 273.1.2.5 SFS Turbo File System Quota Exceeded................................................................................................................. 283.1.2.6 No EIP Bound.................................................................................................................................................................. 283.1.2.7 VPC Quota Used Up...................................................................................................................................................... 283.1.2.8 SFS File System Quota Insufficient.......................................................................................................................... 293.1.2.9 CCE Service Is Abnormal..............................................................................................................................................293.1.2.10 No Available Kafka Instance.................................................................................................................................... 293.1.2.11 Cluster Status Is Abnormal.......................................................................................................................................303.1.2.12 Subnet Unavailable..................................................................................................................................................... 313.1.2.13 Quick Deployment in Progress................................................................................................................................313.1.2.14 Failed to Create CCE Node....................................................................................................................................... 313.1.2.15 CCE Status Check Times Out................................................................................................................................... 323.1.2.16 Insufficient Master Nodes in the AZ of the CCE Cluster................................................................................ 33

4 Abnormal Service Statuses................................................................................................. 344.1 What Can I Do If a BCS Service Is in the Abnormal State?....................................................................................344.2 What Can I Do If a BCS Service Is in the Unknown State?.................................................................................... 374.3 What Can I Do If a BCS Service Is in the EIP abnormal State?.............................................................................384.4 What Can I Do If a BCS Service Is in the Frozen or Cluster frozen State?........................................................394.5 What Can I Do If New Pods Are Abnormal After an Organization or Peer Is Added?.................................41

5 Abnormal Transactions........................................................................................................ 435.1 What Can I Do When Transaction Connections Fail or Time Out?..................................................................... 435.2 What Can I Do If the Network Connection Is Terminated or Rejected During Blockchain Access?........ 48

6 Demo Problems......................................................................................................................496.1 General Checks...................................................................................................................................................................... 496.2 Checking the Java SDK Application Demo................................................................................................................... 506.3 Checking the RESTful API Application Demo.............................................................................................................. 52


Issue 01 (2021-04-26) Copyright © Huawei Technologies Co., Ltd. iii

6.4 Checking the Node.js SDK Application Demo.............................................................................................................53


Issue 01 (2021-04-26) Copyright © Huawei Technologies Co., Ltd. iv

1 Service Usage1.1 What Is Data Aging on Orderers and How Do IEnable It?

Description of Data Aging on Orderers

More and more ledger data is stored on orderers as the business grows. If the webdisk capacity of orderers is not expanded in time, the orderers will experienceperformance deterioration and even stop working. In this case, services cannot runproperly.

To implement data aging on orderers, a threshold must be set. After the size ofthe ledger data on orderers reaches the aging threshold, the earliest block will beremoved every time a new block is generated. In this situation, the size of theledger data on orderers always equals to the threshold. This prevents the impactof ledger data increase on the orderer performance and high costs of a largenumber of web disks.

The data aging function does not affect the service reliability. Data correctness canbe ensured in the case of not more than 10 channels and high concurrency,meeting service requirements in most scenarios.

Method of Enabling Data Aging on Orderers

When deploying a BCS service, set Consensus Mechanism to Kafka (CFT) andEnable Data Aging on Orderers to Yes, and set the data aging threshold, asshown in the following figure. The data aging function of orderers is enabled afterthe service is deployed successfully.

Blockchain ServiceFAQs 1 Service Usage

Issue 01 (2021-04-26) Copyright © Huawei Technologies Co., Ltd. 1

1.2 How Do I Clear Residual Log Files After a BCSService Is Deleted?

After a BCS service is deleted, log files are not automatically deleted from thecluster nodes. You are advised to manually delete the residual files to save space.

Use the remote login tool to log in to each cluster node used by the deleted BCSservice, and check whether there are residual log files in the following paths:

/var/paas/sys/log/baas-agent/var/paas/sys/log/baas-restapi/var/paas/sys/log/baas-service

If residual log files exist, run the following command to delete them:

rm -rf /var/paas/sys/log/baas-agent /var/paas/sys/log/baas-restapi /var/paas/sys/log/baas-service

1.3 What Can I Do If the Marbles Game Fails to BeInstalled in the Walkthrough?

Symptom

When I install and instantiate the chaincode after creating a cluster and BCSservice on the Walkthrough page of the BCS console, a message is displayed,saying "A chaincode with the same name already exists. Enter another name."

Analysis

If the ECS node is restarted or the data plane is upgraded after chaincodeinstallation, the chaincode pod may be deleted and cannot be automaticallyadded after deletion. In this case, chaincode installation is suspended, causing afailure of the Marbles application installation.



SolutionDelete the BCS service (marbles) created for this application and perform thewalkthroughs again. Alternatively, perform the following operations to restart thepod of the chaincode:

1. Log in to the server where the marbles service is deployed.2. Upload and decompress the recover_marbles_ccpod.zip package. Switch to

the directory where the files retrieved by decompression are stored, run thechmod +x recover_marbles.sh command to modify the permissions to therecover_marbles.sh file, and run the ./recover_marbles.sh command.

1.4 How Many Quotas Do I Have for the BCS?Quotas are enforced for service resources available to users on HUAWEI CLOUD toimprove efficiency of resource usage. The following table lists the default quotasof a BCS service.

Table 1-1 Default quotas of a BCS service

Resources Maximum Amount

Instances 5

Invitations 5

Channels 10

Organizations 10

If the quotas cannot meet your business requirements, submit a service ticket toincrease quotas.

1. Log in to the BCS console.In the upper right corner of the page, choose Resources > My Quotas.

2. View the used and total quotas of BCS resources on the displayed ServiceQuota page.



https://bcs.obs.cn-north-1.myhuaweicloud.com/marbles/recover_marbles_ccpod.zip

3. If a quota cannot meet your business requirements, click Increase Quota.

1.5 How Can I Enable Automatic Backup and RestoreData of an SFS Turbo File System?

Enabling Automatic Backup

If you select SFS Turbo for Volume Type and Create SFS Turbo File System forthe network storage of a peer organization when purchasing a BCS service, youare advised to enable the automatic backup function of SFS Turbo on the SFSconsole. If this function is enabled, the system automatically backs up file systemdata on the specified days. If file system data is deleted by mistake orcontaminated, you can use the backup to restore the data, ensuring properrunning of the BCS service.

After creating an SFS Turbo file system on the SFS console, import it on the CCEconsole before resuming BCS service purchase. The following figure shows how toimport an SFS Turbo file system.

NO TE

If you select SFS Turbo for Volume Type and Automatically create SFS Turbo file systemfor the network storage of a peer organization, the automatic backup function is enabledby default, and the data is backed up at 02:00 every day.

Restoring Data1. Locate the BCS service on the Service Management page of the BCS console,

and choose More > Hibernate.



2. Go to the SFS console, click the SFS Turbo file system, locate the backupgenerated at the desired time, click Restore in the Operation column, andclick Yes.

Wait until the data is restored. The file system is unavailable during datarestore. After the restore is completed, the file system will become availableagain.

3. After the file system becomes available, go to the Service Management pageof the BCS console, and choose More > Wake to wake up the service.

NO TE

● Data will be restored to the state at the backup time, and the modifications andnew data added after the backup time will be lost. The file system is unavailableduring data restore.

● If a file system is deleted, its data cannot be restored from the backup.

● Each SFS Turbo file system supports a maximum of 20 backups. If the data isbacked up when 20 backups exist, the earliest backup will be deleted. For details,see the backup function description of the SFS service.

1.6 How Do I Check Whether the ICAgent Is Installedfor the Cluster?

ICAgent is a log collector. It runs on each host to collect metrics, logs, andapplication performance data in real time. If ICAgent is not installed for the clusterused by a BCS service, the log data aging and O&M data collection functions maybecome unavailable, the root directory space may be exhausted, and the servicemay be interrupted.

Perform the following procedure to check the ICAgent status of the cluster. If thestatus is Uninstall, install the ICAgent at the earliest.

Procedure1. Click O&M Center in the navigation pane of the BCS console.2. On the AOM console, choose Configuration Management > Agent

Management, select the cluster in the upper right corner, and check theICAgent status.– If the ICAgent status is Running, the ICAgent has been installed and is

running properly.



– If the ICAgent status is Uninstall, refer to Installing the ICAgent toinstall the ICAgent.

1.7 How Do I Enable the IPv6 EIP Function?After the IPv6 EIP function is enabled, you will obtain an extra IPv6 EIP. ExternalIPv6 addresses can access cloud resources through this IPv6 EIP. To enable the IPv6EIP function for a BCS service, perform the following steps:

Step 1 Enable the IPv6 EIP function.● For an existing EIP

On the EIPs page of the Network Console, locate the target EIP, chooseMore > Enable IPv6 EIP in the Operation column.

● For a new EIPOn the Buy EIP page, select Enable IPv6 Internet access.

Step 2 Go to the Service Management page of the BCS console, locate the BCS serviceto which the EIP is bound, and choose More > Change Access Address. Confirmthat the bound EIP is the same as the EIP for which the IPv6 EIP function has beenenabled.

NO TE

This step is required for both existing and new BCS services.



https://support.huaweicloud.com/intl/en-us/usermanual-aom/aom_02_0012.html

----End

1.8 How Do I Upgrade a BCS Service from Fabric v1.1.0to Fabric v1.4.0?

Existing BCS services of Fabric v1.1.0 can be upgraded to v1.4.0. Fabric v1.1.0 willnot be supported for new BCS services. Only Fabric v1.4.0 will be supported.

For existing consortium blockchains of v1.1.0, an invitee can still create ablockchain of v1.1.0 and join the consortium. If one party in a consortiumblockchain has upgraded to v1.4.0, all consortium members must also upgrade tov1.4.0. Otherwise, transactions will fail.

Upgrading a BCS Service of Fabric v1.1.01. On the Service Management page, choose More > Upgrade.2. Choose a target version (3.x.x) which corresponds to Fabric v1.4.0. Check the

box next to I confirm that I want to upgrade this service between majorversions.To upgrade between major versions for a consortium blockchain, you mustreach consensus with other members in the same blockchain and check thebox next to I have reached consensus with other members in theconsortium.



After the service is upgraded, ensure that other members in the consortiumwill also upgrade their versions soon. If the versions are inconsistent,transactions will fail.

Configuring Applications1. Configure and download the Fabric v1.4.0 SDK file.

After the upgrade to v1.4.0, the v1.1.0 SDK file can no longer be used. Youmust download the v1.4.0 SDK file to replace the original one.

a. Click Download Configuration in a service card.



b. Select SDK Configuration File, and specify the peers, chaincode name,certificate path as required.

c. Click Download.2. Download the Fabric source code package.

Download link: https://github.com/hyperledger/fabric– Golang

Use the downloaded fabric-sdk-go v1.4.0 to replace the original fabric-sdk-go in the vendor > github.com > hyperledger directory of theapplication project file.

– JavaUse the downloaded fabric-sdk-java v1.4.0 to replace the original fabric-sdk-java under lib in the application project file.

3. Disable the event service function.After the upgrade to v1.4.0, the event service function of v1.1.0 will no longerbe supported.– Golang

The event hub function is no longer supported. Comment out relatedcode.//eventHub, err := getEventHub(client, channelID, session) The v1.1.0 NewChannelClient method will also become unsupported. Make the following modifications:Fabric v1.1:sdk, err := fabapi.NewSDK(sdkOptions) chClient, err = sdk.NewChannelClient(channelID, userId)Fabric v1.4:sdk, err := fabsdk.New(config.FromFile(configFile),fabsdk.WithOrgid(orgId)) clientChannelContext := sdk.ChannelContext(channelID,fabsdk.WithUser(userId)) client, err := channel.New(clientChannelContext)

– JavaThe event hub function is no longer supported. Comment out relatedcode.//EventHub eventHub = client.newEventHub("eventhub", BCSConfig.EVENTHUB1_ADDRESS, eventhub1Prop)



https://github.com/hyperledger/fabric

1.9 What Can I Do If I Can't Open the BlockchainManagement Console?

Symptom

The Blockchain Management console cannot be opened.

Fault Locating

1. Check whether you are using the Internet Explorer to log in to theBlockchain Management console.

2. Check whether the BCS service status is abnormal.

Solution1. Check whether you are using the Internet Explorer to log in to the Blockchain

Management console.

If you use the Internet Explorer, you may fail to open the BlockchainManagement login page and see a message indicating that the certificate isuntrusted. In this case, you can click here to resolve the problem.

2. Check whether the BCS service status is abnormal.

If the BCS service is in the Abnormal, EIP abnormal, Frozen, or Unknownstate, the Blockchain Management console will become unavailable. Fordetails, see Abnormal Service Statuses.

1.10 What Should I Do If My BCS Service Remains inthe Creating State?

The possible cause is that the disk fails to be mounted.

If the DNS address in the Pod zone is incorrectly configured, the domain namecannot be resolved and the disk fails to be mounted. Run the following commandto check the DNS address:

vi /etc/resolve.conf

1.11 What Should I Do If a Peer Restarts Frequentlywith the Error Message "PanicDB not exist"?

1. Go to the /home/paas/evs/baas/{Service ID}/{Container ID}/ directory ofthe peer container and delete the production folder.

2. Restart the peer and agent containers, obtain the ledger again, and add thepeer to the channel.



https://support.microsoft.com/en-us/help/3071338/internet-explorer-11-adds-support-for-http-strict-transport-security-s

1.12 What Can I Do If the Block Height Is InconsistentBetween Peers Due to Gossip Exceptions?

1. Run the following command to check the block height of the peer and thencompare it with that of other peers. If there is a difference, block retrievingmay have stopped or delayed.

peer channel getinfo –c {Channel Name}2. Restart the peer and obtain the blocks again. If the fault persists, proceed to

steps 3 to 5.

3. Go to the peer container. In the /etc/hyperledger/fabric/ directory, configurethe following parameters in the core.yaml file to synchronize blocks from theorderer to the peer:useLeaderElection: falseorgLeader: true

4. Run the following command to query the process ID of peer node start:

ps –ef

5. Run the following command to restart the peer process:

kill -9 {pid}

1.13 What Can I Do If the CPU Usage of a BlockchainNode Reaches 100%?

The user node may have been attacked by viruses. If this happens, perform thefollowing operations:

● Use strong passwords that meet the requirements for all accounts (includingsystem accounts and application accounts).

● Use security groups to control access over specific ports. For special serviceports, use fixed source IP addresses, VPNs, or bastion hosts to establish yourown O&M channel.

● Periodically back up data (VM internal backup, remote backup, and backupon and off the cloud) to protect data against encrypting ransomware attacks.

1.14 Why Can't I Log In to the Blockchain ManagementConsole?

You may need to perform extra steps in your browser before you can be redirectedto the Blockchain Management console.

● Internet Explorer

NO TE

These instructions are for reference only. The actual browser pages may varydepending on browser versions, but the operations are similar.



a. Open Internet Explorer and enter the address of the BlockchainManagement console in the address box.

b. Click More information > Go on to the webpage and the login pagewill be displayed.

● Google Chrome

NO TE

These instructions are for reference only. The actual browser pages may varydepending on browser versions, but the operations are similar.

a. Open Google Chrome and enter the address of the BlockchainManagement console in the address box.

b. Click Advanced.



c. Proceed to the login page.

1.15 How Do I Reset the Management Password?1. On the Service Management page, locate a service card and choose More >

Reset Management Password.

2. Enter a new password and confirm the password.



1.16 BCS.4009100: System Error

Symptom

A system error message is displayed on the Service Management page.

Common Causes and Solutions

Scenario 1: The error occurs when you click any button on the ServiceManagement page.

Possible cause 1: The RegionLB component is abnormal.

Solution: Check the buttons on the AOM, CCE, and ServiceStage consoles. Ifsimilar errors occur, contact the RegionLB O&M personnel.

Possible cause 2: The BCS backend is abnormal and does not respond to requests.

Solution: Press F12, choose the Network tab, and check the request for which anerror is reported. Provide the headers and preview information to the BCS O&Mpersonnel.

Scenario 2: The error occurs only when you click some buttons on the ServiceManagement page.

Solution: Press F12, choose the Network tab, and check the request for which anerror is reported. Provide the headers and preview information to the BCS O&Mpersonnel.

1.17 How Do I Change the Name of a BCS Service?Currently, the name of a BCS service cannot be changed. To use a different namefor your BCS service, you can only delete the BCS service and create another onewith a new name.



1.18 How Do I Resolve a Reference Conflict DuringChaincode Installation for a BCS Service of Fabric v1.4?

SymptomWhen a Go chaincode is installed on a BCS service of Fabric v1.4, the errormessage "BCS.4002070 Failed to install the chaincode. The vendor/github.com/.....go file in the installation package is imported repeatedly." isdisplayed.

Root CauseIf the chaincode installation file carries a vendor directory, the chaincodereferences packages from the vendor directory during compilation. If the packagesreferenced in the vendor directory are the same as those in the HyperledgerFabric v1.4 packages referenced in the kernel environment, a package referenceconflict occurs. As a result, the chaincode fails to be installed.

The following packages cannot be reference in the vendor directory of thechaincode installation file:

● github.com/hyperledger/fabric/bccsp/● github.com/hyperledger/fabric/bccsp/utils/● github.com/hyperledger/fabric/bccsp/sw/● github.com/hyperledger/fabric/bccsp/sm/● github.com/hyperledger/fabric/bccsp/signer/● github.com/hyperledger/fabric/bccsp/openssl/● github.com/hyperledger/fabric/bccsp/factory/● github.com/hyperledger/fabric/common/util/● github.com/hyperledger/fabric/common/ledger/util/● github.com/hyperledger/fabric/common/ledger/util/leveldbhelper/● github.com/hyperledger/fabric/common/ledger/blockledger/json/● github.com/hyperledger/fabric/common/ledger/blkstorage/fsblkstorage/● github.com/hyperledger/fabric/common/errors/● github.com/hyperledger/fabric/common/decrypt/● github.com/hyperledger/fabric/common/configtx/● github.com/hyperledger/fabric/common/channelconfig/● github.com/hyperledger/fabric/common/cauthdsl/● github.com/hyperledger/fabric/core/ledger/ledgerstorage/● github.com/hyperledger/fabric/core/ledger/kvledger/● github.com/hyperledger/fabric/core/ledger/kvledger/txmgmt/validator/

statebasedval/● github.com/hyperledger/fabric/core/ledger/kvledger/txmgmt/txmgr/

lockbasedtxmgr/



● github.com/hyperledger/fabric/core/ledger/kvledger/txmgmt/statedb/stateleveldb/

● github.com/hyperledger/fabric/core/ledger/kvledger/txmgmt/statedb/statecouchdb/

● github.com/hyperledger/fabric/core/ledger/kvledger/txmgmt/statedb/commontests/

● github.com/hyperledger/fabric/core/ledger/kvledger/txmgmt/privacyenabledstate/

● github.com/hyperledger/fabric/core/ledger/kvledger/history/historydb/● github.com/hyperledger/fabric/core/ledger/kvledger/● github.com/hyperledger/fabric/core/ledger/cceventmgmt/● github.com/hyperledger/fabric/core/container/util/● github.com/hyperledger/fabric/core/config/● github.com/hyperledger/fabric/core/common/ccprovider/● github.com/hyperledger/fabric/core/comm/● github.com/hyperledger/fabric/core/comm/testdata/certs/● github.com/hyperledger/fabric/core/chaincode/shim/",● github.com/hyperledger/fabric/core/chaincode/platforms/● github.com/hyperledger/fabric/core/chaincode/platforms/util/● github.com/hyperledger/fabric/core/chaincode/platforms/golang/● github.com/hyperledger/fabric/extension/● github.com/hyperledger/fabric/msp/● github.com/hyperledger/fabric/protos/utils/● github.com/hyperledger/fabric/protos/peer/● github.com/hyperledger/fabric/protos/orderer/

Solution

Delete the duplicate packages from the vendor directory in the chaincodeinstallation file.

1.19 Why Is "TLS handshake failed" RepeatedlyDisplayed in the Service Log?

Symptom

The error message "TLS handshake failed" is repeatedly displayed in the servicelog.

Root Cause

The inviting party has dismissed the consortium and created a new BCS service.However, the BCS service of the invitee still exists and repeatedly sends incorrectnetwork requests to the new BCS service of the inviting party.



SolutionThe inviting party changes the EIP or creates another BCS service in a differentCCE cluster.

1.20 How Do I View Chaincode Logs If My BCS ServiceUses Fabric v2.0?

SymptomChaincode container logs of a Fabric v2.0 BCS service cannot be found on theAOM console.

Root CauseCurrently, non-Fabric-v2.0 BCS services use Kubernetes to start chaincodecontainers, whereas Fabric v2.0 BCS services use Docker. The use of Docker isconsistent with the open-source Hyperledger practice, and improves the stabilityof chaincode containers. On the AOM console, only the log files of the chaincodecontainers started using Kubernetes are displayed. Therefore, you cannot view thelog files of chaincode containers started using Docker.

SolutionTo enable users to view chaincode logs on the AOM console for troubleshooting,BCS outputs the run logs of a chaincode to the run logs of the peer where thechaincode is installed.

Search the peer logs for the keyword "[peer.chaincode.dev-peer-Organization ID-Peer ID-Chaincode Name-Chaincode Version]. For example, you can search for thekeyword "[peer.chaincode.dev-peer-964fe19e96d4e28ffc5dd590fd232d6a062e6fea-0-benchmark-1.0]" to find thecorresponding chaincode log, as shown in the following figure:



2 Consultation2.1 What Is Blockchain?

A blockchain is a decentralized and immutable distributed ledger, which does notrequire trust between participants to carry out transactions.

It can be regarded as a distributed database where data is almost impossible tochange. Data is distributed to store and record and maintained by all blockchainparticipants.

Trust can be built among participants thanks to the blockchain technology. Theparticipants in a blockchain consortium are connected to build a peer-to-peervalue transfer network. That is why blockchain is recognized as a trust creator andcornerstone of the Internet of Value. It will offer great opportunities as well ashuge challenges to the financial industry and even the whole society.

Blockchain ServiceFAQs 2 Consultation


2.2 What Benefits Can Blockchain Bring?● Improved efficiency: Transactions can be completed almost in real time.● Lowered costs: The expenditure on the intermediary is cut.● Reduced risks: Risks caused by tampering, fraud, and cybercrimes are reduced.● Enhanced mutual trust: Shared, distributed transaction ledgers build trust

among transaction participants.● Transparent audit: Audit institutions can audit the immutable ledgers at any

time.

2.3 How Do I Determine Whether a Blockchain IsNecessary?

To determine whether the blockchain technology is suitable for your project,answer the following questions in sequence:

● Need multiple parties share data?Will all business participants benefit from a complete and reliable recordsharing system?

● Need multiple parties update data?Will data accuracy and update timeliness be enhanced if multiple participantscan record and propagate concurrent transactions?

● Must data be verified?Can tamper-proof transactions in an untrusted environment improve thetransaction throughput and reliability of partners?

● Can a central institution be removed?Is removal of a central institution helpful to reduce costs and transactioncomplexity?

If your answer is "Yes" for all of the above questions, then your project needs theblockchain technology.

2.4 What Underlying Framework Is Used for HUAWEICLOUD BCS?

HUAWEI CLOUD BCS uses the HyperLedger open-source framework.

HyperLedger is a blockchain open-source project hosted by the Linux Foundationto establish an underlying architecture for the distributed ledger platform orientedto multiple application scenarios. Hyperledger has sub-projects includingHyperledger Fabric, the most important one, and many other related projectsderived on top of it. Developers from various sectors, such as finance, banking, IoT,supply chain, and manufacturing, have contributed towards this project seeking tobuild cross-field blockchain applications.

Based on the HyperLedger framework, Huawei Cloud BCS offers a highly availableand secure blockchain platform boasting a superb performance.



2.5 What Consensus Mechanisms Does HUAWEI CLOUDBCS Support?

BCS provides the following consensus mechanisms to adapt to diverse scenarios:

● SOLO: Only one orderer is available, and therefore, fault tolerance is notsupported. Solo is recommended for testing. It supports Fabric v1.4.0.

● FBFT: Requires 4 to 10 orderers for transaction ordering and tolerates faults ata maximum of (N – 1)/3 orderers, where N indicates the total number oforderers. It supports Fabric v1.4.0 and v2.0.

● Kafka (CFT): Orders transactions using Kafka clusters. Multiple orderers canfunction as Kafka cluster clients to share loads, ensuring service reliability.Kafka enables higher horizontal scalability. It supports Fabric v1.4.0.

● Raft (CFT): A CFT ordering service that tolerates faults at a maximum of (N –1)/2 orderers, where N indicates the total number of orderers. It supportsFabric v2.0.

NO TE

Fabric v1.4.0 does not support Raft (CFT), and Fabric v2.0 does not support SOLO and Kafka(CFT).

2.6 What Are the BCS Deployment Specifications?HUAWEI CLOUD BCS has the following deployment specifications:

● Only one BCS service can be deployed in a container cluster.● Other specifications, such as the quantities of organizations, peers, channels,

and orderers, vary with the editions. For details, see Edition Specifications.

2.7 How Do I Update a Chaincode If It Contains Bugs?BCS supports chaincode upgrade. If you need to fix bugs in a chaincode, you canupload a new code package to update the chaincode.

2.8 Can All Blocks Be Saved As More and More BlocksAre Created?

The increasing number of transactions will lead to blockchain growth and requirelarger storage space. To ensure all the data is stored, you can:

● Expand the storage space.● Back up data.



https://support.huaweicloud.com/intl/en-us/productdesc-bcs/bcs_productdesc_0007.html

2.9 Can BCS Services Deployed on the Public CloudAccess Blockchain Nodes on Other Clouds?

BCS services now can be deployed only on the public cloud. Each user can deploymultiple BCS services. Multiple public cloud users' BCS services can form aconsortium blockchain.

HUAWEI CLOUD-dominated multi-cloud hybrid deployment of BCS services will besupported later, but the launch time is not determined yet.

Blockchain applications of other vendors cannot connect to the BCS.

2.10 What Competitive Advantages Does HUAWEICLOUD BCS Have?

BCS provides multiple options of consensus algorithms, visualized smart contract(chaincode) management, security, and privacy protection (using Chinesecryptographic algorithms, homomorphic encryption, and zero-knowledge proofs).

2.11 In Which Direction and What Capabilities WillHUAWEI CLOUD BCS Develop?

BCS will improve its competitiveness in terms of availability, security, performance,and blockchain ecosystem (such as the smart contract library and blockchain toolkits). It will continuously develop to provide underlying technology services forenterprise-grade commercial blockchains.

2.12 What Are the Specifications of VMs to BePurchased for BCS?

Before deploying a BCS service, purchase virtual machine (VM) resources to runthe service. VMs of the following specifications are recommended.

Table 2-1 Suggestions on VM purchase

Your BusinessPhase

ConsensusAlgorithm

Recommended VM Specifications(Minimum)

POC test SOLO 1 VM with 4 vCPUs and 8 GB memory

POC test FBFT 1 VM with 8 vCPUs and 16 GB memory

POC test Kafka (CFT) 2 VMs, each with 4 vCPUs and 8 GBmemory



Your BusinessPhase

ConsensusAlgorithm

Recommended VM Specifications(Minimum)

Commercialuse

- To be determined based on the servicescale and number of users. You cancontact the BCS O&M personnel toseek help.

2.13 How Do I Get Access to the Partners of HUAWEICLOUD BCS for More Services?

If you have requirements for service chaincode or client app design anddevelopment, reach us by the following email box, then BCS and its partners willprovide you with comprehensive solutions based on your business and HUAWEICLOUD advantages and features:

[email protected]

2.14 When Do I Need to Hibernate or Wake a Service?

Scenario

You can hibernate a pay-per-use BCS service when it is not required temporarilyand wake it when you need to use it. A service in hibernation is unavailable.

Benefits

BCS services in hibernation do not incur any management fees. This enablesaccurate pay-per-use billing and helps enterprises reduce unnecessary investments.

NO TE

After a service is hibernated, the resources configured for it such as ECS and cloud hard diskresources are billed according to their billing modes.

2.15 What Ledger Storage Modes Are Supported?File database (GoLevelDB) and NoSQL (CouchDB) are available for ledger storage.

● File database: The Fabric native storage mode is used. Historical transactiondata is stored in the blockchain, and status data is stored in the LevelDB.

● NoSQL: The CouchDB storage mode supported by the Fabric is used to storetransaction data and status data. Each CouchDB database is a collection ofindependent documents. Each document maintains its own data and self-contained schema.



2.16 What Are the Differences Between ChannelIsolation and Privacy Protection?

Channel isolation: A channel isolates the ledger data of a transaction from othertransaction data in a consortium blockchain to ensure confidentiality. Eachchannel can be considered a sub-blockchain and corresponds to a specific ledger.The ledger in a channel is invisible to other channels.

Privacy protection: Privacy is ensured within each channel because differentmembers in a channel can have different access permissions. For example,member A has the permissions to access certain data, but member B, who doesnot have relevant permissions, cannot access the specified data.

In short, privacy protection isolates data for a member from other members insame channel, while channel isolation isolates data for all members in a channelfrom other channels.

2.17 Can I Invite Individual Users to Join a Consortium?Yes. You can invite any public cloud users (individual and enterprise users) to joina consortium.

2.18 How Is the Performance of BCS?The following performance data is obtained from the pressure test carried out byusing a 32 vCPUs | 64 GB ECS and two clients.

Table 2-2 BCS performance in different scenarios

Scenario Performance

Security Mechanism+Consensus Mechanism

Maximum Concurrency TPS (ConsistencyMaintained)

ECDSA+Kafka 400 11,967

ECDSA+FBFT 50 6504

Chinese cryptographicalgorithms+Kafka

300 9982

Chinese cryptographicalgorithms+FBFT

50 5698



3 Purchases and Deployment3.1 What Can I Do If I Fail to Purchase a BCS Service?

3.1.1 General Checks

SymptomA BCS service fails to be purchased.

Fault LocatingCheck item 1: Check whether the account is in arrears.

Check item 2: Check whether the permissions of the IAM user are insufficient.

Check item 3: Check the details error information.

Solution● Check item 1: Check whether the account is in arrears.

a. Log in to the BCS console and click Billing Center in the upper part ofthe page.

If Account Balance is zero or less than the price displayed when youpurchase the BCS service, the purchase will fail.

Blockchain ServiceFAQs 3 Purchases and Deployment


b. In the Pending Orders area, click Pay Now. On the Orders page that isdisplayed, select the order to be paid and complete the payment.

If the payment fails and a message is displayed indicating that thebalance is insufficient, the purchase will also fail.

c. In the Pending Renewal area, click View All. On the displayed page,select the resources to be renewed and click Renew.

● Check item 2: Check whether the permissions of the IAM user are insufficient.If the BCS service is purchased by using an IAM user, obtain permissions byfollowing instructions in Permissions Management.

● Check item 3: Check the details error information.Log in to the BCS console. In the navigation pane, choose ServiceManagement. Above the service list, click the number next to Servicedeployment failures. Then, click View Details in the same row as the targetrecord. In the displayed window, click View Cause to analyze the failure.The following lists the detailed errors. Click the links to view thecorresponding solutions.Error 1: [CreateContainerCluster] CCE has no quotaError 2: [CreateContainerCluster] Create Cluster failError 3: [CreateStorageInstance]Create PVC fail,timeoutError 4: [CreateBlockchainService]cluster is already usedError 5: [CreateStorageInstance] PostReqNoCert: response status 400 not OK,resp is: {"errCode":"SFS.TURBO.0010","errMsg":"instance quota exceeds"}Error 6: [CreateEIP]no down eip, need buy oneError 7: [CreateContainerCluster] vpc no quotaError 8: [CreateStorageInstance] sfs have no quotas when ImproveCCEError 9: [CreateContainerCluster]visitInterface Fail,/api/v2/projects/xxx/clusters response state not OK,code:500Error 10: [CreateKafkaInstance]can not find the kafka instanceid by jobinforError 11: [CreateBlockchainService]DeleteKubeResource failed, clusterID:xxx,resourceName: xxx, err:DELETE:response status 400 not OK, resp is:ClusterStatus Not ReadyError 12: [CreateContainerCluster]Invalid subnet id xxx



https://support.huaweicloud.com/intl/en-us/usermanual-bcs/bcs_usermanual_0020.html

Error 13: [CreateBlockchainService]one OneStep is processing under thisdomain(xxx),please wait it finished and do it again

Error 14: [CreateContainerCluster]creating node machine failed

Error 15: [CreateContainerCluster]cce status check timeout whencheckClusterJobStatus...

Error 16: [CreateContainerCluster] VisitInterface Fail, PostReqNoCert:response status 400 not OK, resp is: {"message":"\u003cCCE_CM.4000311\u003e No available master flavors | The amount of available masterflavors are not enough to create a cluster, in specified azs, need 1, has0","reason":"BadRequest","code":400}

3.1.2 Detailed Checks

3.1.2.1 CCE Cluster Quota Used Up

Refund Description

If a BCS service fails to be created, the deducted fee will be returned to theaccount within 0.5 to 1 hour.

Symptom

The BCS service fails to be created because the CCE cluster quota has been usedup.

Solution

Apply for a higher cluster quota and purchase a BCS service again.

Log in to the CCE console. In the upper right corner of the page, choose Resources> My Quotas. On the displayed page, click Increase Quota. On the CreateService Ticket page, submit a service ticket.

3.1.2.2 Failed to Create a Cluster

Refund Description




SymptomThe CCE cluster fails to be created during BCS service creation.

SolutionCreate a cluster first and select the created cluster when buying a BCS service.

Log in to the CCE console and click Buy Cluster. For details, see Creating aKubernetes Hybrid Cluster.

3.1.2.3 Failed to Create a PVC

Refund DescriptionIf a BCS service fails to be created, the deducted fee will be returned to theaccount within 0.5 to 1 hour.

SymptomThe PVC fails to be created during BCS service creation.

SolutionPerform the following operations before buying a BCS service:

1. Create an SFS file system:Log in to the SFS console and click Create File System or Buy ResourcePackage. For details, see Create a File System.

2. Buy a CCE cluster:Log in to the CCE console and click Buy Cluster. For details, see Creating aKubernetes Hybrid Cluster.

3. Import the SFS file system to the cluster:In the navigation pane of the CCE console, choose Resource Management >Storage > SFS. Click Import, select the target cluster and the project, selectthe target PVC, and click OK.

3.1.2.4 Cluster Already In Use


SymptomThe BCS service fails to be created because the CCE cluster has already been used.

SolutionSolution 1: Select an unused CCE cluster when creating a BCS service.



https://support.huaweicloud.com/intl/en-us/qs-cce/cce_qs_0008.htmlhttps://support.huaweicloud.com/intl/en-us/qs-cce/cce_qs_0008.htmlhttps://support.huaweicloud.com/intl/en-us/qs-sfs/en-us_topic_0034428727.htmlhttps://support.huaweicloud.com/intl/en-us/qs-cce/cce_qs_0008.htmlhttps://support.huaweicloud.com/intl/en-us/qs-cce/cce_qs_0008.html

Solution 2: Create a cluster first and select the created cluster when buying a BCSservice.

To create a cluster:


3.1.2.5 SFS Turbo File System Quota Exceeded


SymptomThe BCS service fails to be created because the SFS Turbo quota limit is exceeded.

SolutionApply for a higher SFS Turbo file system quota and purchase a BCS service again.

Log in to the SFS console. In the upper right corner, choose Resources > MyQuota > Increase Quota. On the Create Service Ticket page, submit a serviceticket.

3.1.2.6 No EIP Bound


SymptomThe BCS service fails to be created because no EIP is bound.

SolutionBuy a BCS service again.

3.1.2.7 VPC Quota Used Up


SymptomThe BCS service fails to be created because the VPC quota has been used up.



https://support.huaweicloud.com/intl/en-us/qs-cce/cce_qs_0008.htmlhttps://support.huaweicloud.com/intl/en-us/qs-cce/cce_qs_0008.html

Solution

Apply for a higher VPC quota and purchase a BCS service again.

Log in to the VPC console. In the upper right corner, choose Resources > MyQuota > Increase Quota. On the Create Service Ticket page, submit a serviceticket.

3.1.2.8 SFS File System Quota Insufficient

Refund Description


Symptom

The BCS service fails to be created because the SFS quota is insufficient.

Solution

Apply for a higher SFS file system quota and purchase a BCS service again.

Log in to the SFS console. In the upper right corner, choose Resources > MyQuota > Increase Quota. On the Create Service Ticket page, submit a serviceticket.

3.1.2.9 CCE Service Is Abnormal

Refund Description


Symptom

The BCS service fails to be created because CCE is abnormal.

Solution

Create a cluster first and select the created cluster when buying a BCS service.


3.1.2.10 No Available Kafka Instance

Refund Description





Symptom

The BCS service fails to be created because no Kafka instance is available.

Solution

Create a Kafka instance first and select the created Kafka instance when buying aBCS service.

For details, see Buying an Instance.

3.1.2.11 Cluster Status Is Abnormal

Refund Description


Symptom

The BCS service fails to be created because the cluster status is abnormal.

Solution● Solution 1: Check whether the cluster is running properly.

In the navigation pane of the CCE console, choose Resource Management >Clusters to view the cluster status.

If the cluster status is normal, purchase a BCS service again. If the clusterstatus is abnormal, submit a service ticket for consultation.

● Solution 2: Select an unused CCE cluster when creating a BCS service.



https://support.huaweicloud.com/intl/en-us/usermanual-kafka/kafka-ug-180604013.html

3.1.2.12 Subnet Unavailable

Refund Description


Symptom

The BCS service fails to be created because the subnet is unavailable.

Solution

Create a cluster first and select the created cluster when buying a BCS service.



3.1.2.13 Quick Deployment in Progress

Refund Description


Symptom

The BCS service fails to be created because another service is being createdthrough one-click deployment under the account.

Solution

Buy a new BCS service after the current quick deployment completes.

3.1.2.14 Failed to Create CCE Node

Refund Description


Symptom

The BCS service fails to be created because nodes fail to be created in CCE.

Solution● Solution 1: Specify a different AZ when creating a BCS service again.




If the BCS service fails to be created again, submit a service ticket.

● Solution 2: Create a cluster first and select the created cluster when buying aBCS service.



3.1.2.15 CCE Status Check Times Out

Refund Description


Symptom

The BCS service fails to be created because the CCE cluster status check times out.


If the BCS service fails to be created again, submit a service ticket.

● Solution 2: Create a cluster first and select the created cluster when buying aBCS service.





https://support.huaweicloud.com/intl/en-us/qs-cce/cce_qs_0008.htmlhttps://support.huaweicloud.com/intl/en-us/qs-cce/cce_qs_0008.htmlhttps://support.huaweicloud.com/intl/en-us/qs-cce/cce_qs_0008.htmlhttps://support.huaweicloud.com/intl/en-us/qs-cce/cce_qs_0008.html

3.1.2.16 Insufficient Master Nodes in the AZ of the CCE Cluster


SymptomThe BCS service fails to be created because the master node resources areinsufficient in the AZ of the CCE cluster.


If the BCS service fails to be created again, submit a service ticket.● Solution 2: Create a cluster first and select the created cluster when buying a

BCS service.To create a cluster:Log in to the CCE console and click Buy Cluster. For details, see Creating aKubernetes Hybrid Cluster.




4 Abnormal Service Statuses4.1 What Can I Do If a BCS Service Is in the AbnormalState?

SymptomThe BCS service is in the Abnormal state.

Fault LocatingCheck item 1: Check whether the cluster, storage, and server resources on whichthe blockchain depends are normal.

Check item 2: Check whether the ECS specifications can meet the requirements.

Solution● Check item 1: Check whether the cluster, storage, and server resources on

which the blockchain depends are normal.

a. Check the CCE cluster status.

i. Log in to the CCE console, choose Resource Management >Clusters, and check the status of the cluster where the BCS service isdeployed.

Blockchain ServiceFAQs 4 Abnormal Service Statuses


If the cluster status is abnormal, locate the fault by following theCCE instructions: How Do I Rectify the Fault When the ClusterStatus Is Unavailable?

ii. On the CCE console, choose Resource Management > Nodes, andcheck the status of the node where the BCS service is deployed.

If the node status is abnormal, locate the fault by following the CCEinstructions: What Should I Do If a Cluster Is Available But SomeNodes Are Unavailable?

b. Check the ECS status.Log in to the ECS console and check the status of the ECS where theabnormal BCS service is deployed. ECS names usually take the followingformat: Name of the cluster where the BCS service is deployed-Arandom number.

If the ECS is in the Stopped state, start the ECS, wait for about 5 minutes,and check its status again.

c. Check the storage status.

i. Log in to the BCS console, go to the Service Management page, andclick the abnormal service to view its volume type.



https://support.huaweicloud.com/intl/en-us/cce_faq/cce_faq_00039.htmlhttps://support.huaweicloud.com/intl/en-us/cce_faq/cce_faq_00039.htmlhttps://support.huaweicloud.com/intl/en-us/cce_faq/cce_faq_00120.htmlhttps://support.huaweicloud.com/intl/en-us/cce_faq/cce_faq_00120.html

ii. Log in to the CCE console, choose Resource Management >Storage. Click the SFS Turbo tab based on the volume type of theBCS service, and check the status of the file system in the CCE clusterwhere the abnormal BCS service is deployed.

iii. If the SFS Turbo volume is in the Lost state, the state of the BCSservice will be displayed as Abnormal.SFS Turbo:

Solution:Check whether the SFS Turbo file system exists or whether it isfrozen, or contact the SFS customer service.

● Check item 2: Check whether the ECS specifications can meet therequirements.

a. Log in to the ECS where the BCS service is deployed.Log in to the ECS console, locate the target ECS in the ECS list, and clickRemote Login in the Operation column. ECS names usually take thefollowing format: Name of the cluster where the BCS service isdeployed-A random number.

b. Run the top command to check whether the resource usage of anyapplication is too high.



▪ If the CPU or memory usage of the peer, orderer, and baas-agentcontainers exceeds 60% and continues to increase as the transactionquantity increases, the current ECS specifications cannot meet thetransaction requirements. In this case, you need to expand the ECSspecifications.

▪ If there are resources taking up 100% or even higher CPU or memoryusage, contact the ECS customer service to remove unnecessaryresources.

4.2 What Can I Do If a BCS Service Is in the UnknownState?

Symptom

The BCS service is in the Unknown state.

Fault Locating

Check item 1: Check whether the cluster is hibernated.

Check item 2: Check whether the cluster exists.



Solution● Check item 1: Check whether the cluster is hibernated.

a. Log in to the BCS console, go to the Service Management page, andclick the abnormal service. On the service details page, click More andview the name of the cluster used by the service.

b. Log in to the CCE console, choose Resource Management > Clusters,and check the status of the target cluster.

c. If the cluster is in the Hibernating state, the BCS service is in theUnknown state.

d. Wake up the cluster. The BCS service will become normal.

To wake up a cluster, choose More > Wake for the target cluster.

● Check item 2: Check whether the cluster exists.

a. Log in to the BCS console and follow a to view the cluster name of theabnormal service.

b. Log in to the CCE console, choose Resource Management > Clusters,and look for the target cluster.

c. If the cluster where the BCS service is deployed does not exist, the BCSservice status is displayed as Unknown. If the cluster is not manuallydeleted, contact the CCE customer service.

4.3 What Can I Do If a BCS Service Is in the EIPabnormal State?

Symptom

The BCS service is in the EIP abnormal state.



Fault LocatingCheck item: Check whether the EIP has been unbound or released.

1. On the BCS console, choose Service Management. In the card containing thetarget service, choose More > Change Access Address to view the EIP.

2. Go to the Network Console, locate the target EIP, and view its status.

Solution1. If the EIP has been unbound, click Bind in the Operation column of the

target EIP. Then, go back to the BCS console and refresh the ServiceManagement page.

2. If the EIP has been released, it is not displayed in the EIP list. In this case,purchase a new EIP and bind it. For details, see Assigning an EIP. Then, goback to the BCS console. On the Service Management page, choose More >Change Access Address in the card containing the target service. Select thetarget EIP and click OK.

4.4 What Can I Do If a BCS Service Is in the Frozen orCluster frozen State?

SymptomThe BCS service is in the Frozen or Cluster frozen state.

If the account is in arrears, resources are frozen. After you renew the resources,the order status changes to Completed, indicating that the resources have beenunfrozen and the resource status is restored.



https://support.huaweicloud.com/intl/en-us/usermanual-eip/eip_0008.html

Solution1. Log in to the BCS console and click Billing Center in the upper part of the

page.2. In the Pending Renewal area, click View All. On the displayed page, select

the resources to be renewed and click Renew.

3. After the renewal is complete, go to the ECS console and check the status ofthe ECS where the BCS service is deployed. (ECS names usually take thefollowing format: Name of the cluster where the BCS service is deployed-Arandom number.) If the ECS is in the Stopped state, wait for about 5minutes and try again.



4.5 What Can I Do If New Pods Are Abnormal After anOrganization or Peer Is Added?

Symptom

More than 10 minutes after an organization or peer is added, the new podsremain abnormal. As a result, the change on the BCS service times out and theservice status is abnormal. The task details show "BCS(XXX) wait for updatingagent 400 times, stop updating" when an organization has been added or "waitthe expand peer running exceed 100 times, stop waiting" when a peer has beenadded.

Solution

Step 1 Log in to the CCE console, choose Workloads > StatefulSets, select the clusterused by the BCS service, and click the workload used by the new organization orpeer. On the workload details page, view the pod list, and locate the abnormalpod. Check the pod events to find out why the pod fails to be started.

Possible causes include:

1. The storage volume fails to be mounted to the pod.

2. The image fails to be pulled.

3. The health check fails.

Step 2 If the storage volume fails to be mounted to the pod or the health check fails,click Add-ons in the navigation pane to check whether the add-ons of thecorresponding cluster are normal. If the add-ons are normal, go to the next step. Ifthe add-ons are abnormal, uninstall and reinstall them, and then go to the nextstep.

If the image fails to be pulled, check whether the image exists by logging in to thecluster node to manually pull the image or by contacting BCS O&M personnel. Ifthe image exists, go to the next step. If the image does not exist, contact BCSO&M personnel.

Step 3 Locate the abnormal pod in the pod list and click Delete. Wait for a new pod tobe started.

If the new pod is successfully started, switch to the Containers tab page of thepod. If the container status is normal, go to the next step. If the container or podstatus is still abnormal, check the events.

If the pod fails to be started because the storage volume fails to be mounted tothe pod or the health check fails, contact CCE O&M personnel. If the pod fails tobe started because the image fails to be pulled, contact BCS O&M personnel.

Step 4 After the pod becomes normal, choose Workloads > Deployments in thenavigation pane and find the baas-agent workload. On the workload detailspage, click Pods. In the pod list, click Delete. After a new pod is started, return to



the BCS service list on the BCS console and check whether the service is normal. Ifyes, no further action is required. If no, contact BCS O&M personnel.

----End



5 Abnormal Transactions5.1 What Can I Do When Transaction Connections Failor Time Out?

Symptom

Transaction connections fail or time out.

Fault Locating

Check item 1: Check whether the transaction times out after the chaincode isinstantiated for the first time.

Check item 2: Check whether the BCS service status is abnormal.

Check item 3: Check whether the Fabric SDK version used by the client matchesthe BCS service version.

Check item 4: Check whether the ledger of the peer is updated.

Check item 5: Check whether the DB file exists.

Check item 6: Check whether the BCS service uses CouchDB for ledger storageand has been upgraded or restarted.

Solution● Check item 1: Check whether the transaction times out after the chaincode is

instantiated for the first time.

During chaincode instantiation of a v3.0.x BCS service (corresponding toFabric v1.4.0), the container of only one peer in each organization is started.The chaincode of other peers is easy to build and start, which is triggered atthe first transaction endorsement. This process takes a long time, and thetransaction may time out.

Blockchain ServiceFAQs 5 Abnormal Transactions


If you use a Go SDK, this problem does not need to be handled. The SDK willwait for the chaincode container to start, and no timeout will occur.If you use a Java SDK, you can set req.setProposalWaitTime(), the timeoutfor a request to endorse, in your application. In the following figure, thetimeout is set to 60 seconds to avoid transaction failure after the chaincode isinstantiated for the first time.

● Check item 2: Check whether the BCS service status is abnormal.Log in to the BCS console and rectify the fault based on the service status byfollowing instructions provided in What Can I Do If a BCS Service Is in theAbnormal State?

● Check item 3: Check whether the Fabric SDK version used by the clientmatches the BCS service version.Log in to the BCS console. In the navigation pane, choose ServiceManagement. In the card containing the abnormal service, choose More >View Details.



Record the value of Version. Check whether the Fabric SDK version used bythe client is the same as the BCS service version. If the versions areinconsistent, transactions may fail or time out.Solution:Download the Fabric SDK of the version that corresponds to the HyperledgerFabric version of the BCS service.Download link: https://github.com/hyperledger/fabric

● Check item 4: Check whether the ledger of the peer is updated.

a. Log in to the BCS console. In the navigation pane, choose ServiceManagement. In the card containing the abnormal service, click ManageBlockchain. On the Block Browser page, select the abnormal channel,and view the block quantity on the Block List tab page.



https://github.com/hyperledger/fabric

b. Log in to the ECS where the BCS service is deployed, run the docker ps|grep k8s_peer command to check the peer containers, and record the IDof the container where transactions time out.

c. Run the docker exec -it container id /bin/bash command to enter thecontainer.

d. Run the peer channel list command to query the channel to which thepeer is added.

e. Run the peer channel getinfo -c {Channel name} command to checkwhether the ledger of the peer is updated.

If the block quantity in the ledger of the peer is different from thatdisplayed on the Block Browser page, query the block quantity againafter 10 minutes. If the block quantity has not increased over the past 10minutes, the ledger of the peer is not updated due to insufficientresources or high concurrency. As a result, transactions become abnormal.

In this case, submit a service ticket for consultation.

● Check item 5: Check whether the DB file exists.

a. Log in to the ECS where the BCS service is deployed, run the docker ps|grep k8s_peer command to check the peer containers, and record the IDof the container where transactions are abnormal.

b. Run the docker exec -it container id /bin/bash command to enter thecontainer.

c. Run the cd /var/log/baas-service/peer/ command to go to the directorywhere the logs of the peer are stored, and run the ll command to view allfiles.

d. Obtain the hash value and sequence number of the peer.

On the Block Browser page of the Blockchain Management console,view the domain name and sequence number of the peer in the Domainof Peer column in the Peer Status list.



e. The peer log file names take the following format: peer-{hash value}-{serial number}.trace. Run the cat {file name}|grep -C 5 command tosearch for exception information.

If you see "Fail to recover DB: file does not exist", the DB file of the peerdoes not exist. As a result, transactions are abnormal.In this case, submit a service ticket for consultation.

● Check item 6: Check whether the BCS service uses CouchDB for ledger storageand has been upgraded or restarted.If a BCS service is of an earlier version and uses CouchDB for ledger storage,the status data will be lost after the service is restarted, because the statusdata is not stored in the SFS file system. In this case, CouchDB reloads the



block data to generate the status data, and the BCS service is unavailable fora certain period of time.It takes about 2 hours to synchronize data of 150,000 blocks. During datasynchronization, port 7051 of the peer cannot be accessed.Solution:Upgrade the BCS service to the latest version, and this problem will not occurwhen you upgrade or restart the service.

NO TE

When a BCS service is upgraded to the latest version for the first time, the CouchDBcontainer mounts the web disk and synchronizes status data. As a result, the BCSservice is unavailable for a certain period of time. This duration increases linearly asthe block quantity increases. It takes about 2 hours to synchronize data for every150,000 blocks. The block quantity can be viewed on the Block Browser page of theBlockchain Management console.

5.2 What Can I Do If the Network Connection IsTerminated or Rejected During Blockchain Access?

Increase the node bandwidth or host specifications, or reduce the transactionconcurrency.



6 Demo Problems6.1 General Checks

Fault Locating

Check item 1: Check whether the account is in arrears.

Check item 2: Check whether the service status is normal.

Check item 3: Check whether the chaincode is properly instantiated.

Check item 4: Check whether the demo has been modified.

Solution● Check item 1: Check whether the account is in arrears.

a. Log in to the BCS console and click Billing Center in the upper part ofthe page.

If Account Balance is zero or less than the price displayed when youpurchase the BCS service, the purchase will fail.

b. In the Pending Orders area, click Pay Now. On the Orders page that isdisplayed, select the order to be paid and complete the payment.

Blockchain ServiceFAQs 6 Demo Problems


If the payment fails and a message is displayed indicating that thebalance is insufficient, the purchase will also fail.

c. In the Pending Renewal area, click View All. On the displayed page,select the resources to be renewed and click Renew.

● Check item 2: Check whether the service status is normal.Log in to the BCS console. In the navigation pane, choose ServiceManagement. View the status of the target service. For details, seeAbnormal Service Statuses.

● Check item 3: Check whether the chaincode is properly instantiated.

a. Log in to the BCS console. In the navigation pane, choose ServiceManagement. In the card containing the target service, click ManageBlockchain. Enter the password and verification code and click Log In.Then, go to the Chaincode Management page.

b. Click View more in the Instantiation Channel column to view theinstantiation status of the target chaincode.

● Check item 4: Check whether the demo has been modified.Follow the instructions in the next sections to check whether the specifieddemo has been modified.

6.2 Checking the Java SDK Application Demo

Fault Locating1. Check whether the BCS service is named java-sdk-demo, uses the Basic

edition (or Enterprise edition if the security mechanism is Chinesecryptographic algorithms), is a private blockchain deployed in a CCE cluster,and uses Solo for the consensus mechanism.

NO TE

In addition, ensure that the development tools have been correctly installed andconfigured. For details, see Preparation.

To check these details, log in to the BCS console, go to the ServiceManagement page, and click the target service to view its details. For detailsabout the configurations required for this demo, see Java SDK Demo.



https://support.huaweicloud.com/intl/en-us/devg-bcs/bcs_devg_0032.htmlhttps://support.huaweicloud.com/intl/en-us/devg-bcs/bcs_devg_0032.html

2. Check whether the orderer and peer certificates have been downloaded, andwhether the SDK file (java-sdk-demo-sdk-config.zip) has been downloadedto the config directory of the demo project. For details, see sections"Download the SDK configuration" and "Download certificates" underConfiguring the Application.

NO TE

The chaincode name specified when you set the SDK file parameters must be thesame as that specified during chaincode installation.

3. Check whether the path of the Main class has been changed as required. Fordetails, see Deploying the Application.Find the Main.java file in the /javasdkdemo/src/main/java/handler/directory, and change the file path in the following code of the Main class tothe absolute path of the java-sdk-demo-sdk-config.yaml file. Change thebackslashes (\) to slashes (/).helper.setConfigCtx("E:/yourdir/huawei.yaml");

4. If the BCS service uses Chinese cryptographic algorithms, check whether thedependency upon fabric-sdk-java-1.4.1-jar-with-dependencies.jar is addedto pom.xml. To add the dependency, remove the comments on thedependency as shown in the following figure.

5. If timeout occurs occasionally and the transaction interval is long, checkwhether the fault is caused by the connection protection mechanism of athird-party gRPC. The following figure shows the error information.

Solution

In the src\main\java\handler\FabricHelper.java file, add p.put to the samplecode as shown in the following figure. Save the code and perform the transactionagain.



https://support.huaweicloud.com/intl/en-us/devg-bcs/bcs_devg_0032.html#section3https://support.huaweicloud.com/intl/en-us/devg-bcs/bcs_devg_0032.html#section4

p.put("grpc.NettyChannelBuilderOption.keepAliveTime", new Object[] {5L,TimeUnit.MINUTES});

p.put("grpc.NettyChannelBuilderOption.keepAliveTimeout", new Object[] {8L,TimeUnit.SECONDS});

p.put("grpc.NettyChannelBuilderOption.keepAliveWithoutCalls", new Object[]{true});

p.put("grpc.NettyChannelBuilderOption.maxInboundMessageSize", 102400000);

6.3 Checking the RESTful API Application Demo

Fault Locating1. Check whether the BCS service is named demo, uses the Basic or Professional

edition, is a private blockchain deployed in a CCE cluster, uses SOLO for theconsensus mechanism and ECDSA for the security mechanism, and hasenabled support for RESTful APIs. If support for RESTful APIs was not enabledduring BCS service creation, you can still enable it by installing an add-onafter the BCS service is created.To check these details, log in to the BCS console, go to the ServiceManagement page, and click the target service to view its details. For detailsabout the configurations required for this demo, see REST API Demo.

2. Check whether the user certificate has been downloaded and whetherparameters in conf.yaml and main.go have been modified.Download the user certificate by referring to Accessing Blockchain Services.



https://support.huaweicloud.com/intl/en-us/devg-bcs/bcs_devg_0034.htmlhttps://support.huaweicloud.com/intl/en-us/usermanual-bcs/bcs_usermanual_0016.html

For details on how to modify the parameters in the conf.yaml and main.gofiles, see section "Modify parameter settings" under Configuring theApplication.

6.4 Checking the Node.js SDK Application Demo

Fault Locating1. Check whether the BCS service is named node-sdk-demo, uses the Basic

edition, is a private blockchain deployed in a CCE cluster, uses SOLO for theconsensus mechanism and ECDSA for the security mechanism, and uses the2.x.x version (corresponding to Fabric v1.1.0).To check these details, log in to the BCS console, go to the ServiceManagement page, and click the target service to view its details. For detailsabout the configurations required for this demo, see Node.js SDK Demo.

2. Check whether the orderer and peer certificates and the SDK have beendownloaded, and whether the SDK configuration file path in sdk-config.js hasbeen changed.For details, see Deploying the Application and Debugging the Application.

NO TE

The chaincode name specified when you set the SDK file parameters must be thesame as that specified during chaincode installation.



https://support.huaweicloud.com/intl/en-us/devg-bcs/bcs_devg_0034.html#section2https://support.huaweicloud.com/intl/en-us/devg-bcs/bcs_devg_0034.html#section2https://support.huaweicloud.com/intl/en-us/devg-bcs/bcs_devg_0036.htmlhttps://support.huaweicloud.com/intl/en-us/devg-bcs/bcs_devg_0036.html#section3https://support.huaweicloud.com/intl/en-us/devg-bcs/bcs_devg_0036.html#section4

Contents1 Service Usage1.1 What Is Data Aging on Orderers and How Do I Enable It?1.2 How Do I Clear Residual Log Files After a BCS Service Is Deleted?1.3 What Can I Do If the Marbles Game Fails to Be Installed in the Walkthrough?1.4 How Many Quotas Do I Have for the BCS?1.5 How Can I Enable Automatic Backup and Restore Data of an SFS Turbo File System?1.6 How Do I Check Whether the ICAgent Is Installed for the Cluster?1.7 How Do I Enable the IPv6 EIP Function?1.8 How Do I Upgrade a BCS Service from Fabric v1.1.0 to Fabric v1.4.0?1.9 What Can I Do If I Can't Open the Blockchain Management Console?1.10 What Should I Do If My BCS Service Remains in the Creating State?1.11 What Should I Do If a Peer Restarts Frequently with the Error Message "PanicDB not exist"?1.12 What Can I Do If the Block Height Is Inconsistent Between Peers Due to Gossip Exceptions?1.13 What Can I Do If the CPU Usage of a Blockchain Node Reaches 100%?1.14 Why Can't I Log In to the Blockchain Management Console?1.15 How Do I Reset the Management Password?1.16 BCS.4009100: System Error1.17 How Do I Change the Name of a BCS Service?1.18 How Do I Resolve a Reference Conflict During Chaincode Installation for a BCS Service of Fabric v1.4?1.19 Why Is "TLS handshake failed" Repeatedly Displayed in the Service Log?1.20 How Do I View Chaincode Logs If My BCS Service Uses Fabric v2.0?

faqs - 帮助中心首页-华为云 · 2020. 11. 11. · follow the instructions in the next...

Documents