Help Center>
Blockchain Service>
FAQs>
Enhanced Hyperledger Fabric>
Instance Management>
Service Usage>
What Should I Do If My BCS Instance Remains in the Creating State?
Updated on 2022-09-26 GMT+08:00
What Should I Do If My BCS Instance Remains in the Creating State?
The possible cause is that the disk fails to be mounted.
Solution
- Log in to the node in the Cloud Container Engine (CCE) cluster where the BCS instance is deployed, and run the following command to check the DNS address in the POD zone. If the DNS address in the POD zone is incorrectly configured, the domain name cannot be resolved and the disk fails to be mounted.
vi /etc/resolve.conf
- If the fault persists, contact technical support.
Parent topic: Service Usage
Service Usage FAQs
- Which Ports of a Security Group Are Opened When I Create a BCS Instance?
- How Do I Check Whether the ICAgent Is Installed for the Cluster?
- What Can I Do If I Can't Open the Blockchain Management Console?
- What Should I Do If My BCS Instance Remains in the Creating State?
- What Should I Do If a Peer Restarts Frequently with the Error Message "PanicDB not exist"?
- What Can I Do If the CPU Usage of a Blockchain Node Reaches 100%?
- Why Can't I Log In to the Blockchain Management Console?
- BCS.4009100: System Error
- How Can I Obtain Private Keys and Certificates for Enhanced Hyperledger Fabric Blockchains?
- Why Does Chaincode Instantiation Fail When I Deploy a Fabric v1.4 Instance Using a v1.19 CCE Cluster?
- Can All Blocks Be Saved As More and More Blocks Are Created?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
