Help Center/ Blockchain Service/ User Guide (ME-Abu Dhabi Region)/ FAQs/ BCS FAQs/ Instance Management/ Service Usage/ What Should I Do If a Peer Restarts Frequently with the Error Message "PanicDB not exist"?

Updated on 2022-02-21 GMT+08:00

View PDF

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

Go to the /home/paas/evs/baas/{Service ID}/{Container ID}/ directory of the peer container and delete the production folder.
Restart the peer and agent containers, obtain the ledger again, and add the peer to the channel.

Parent topic: Service Usage

Previous topic: What Should I Do If My BCS Instance Remains in the Creating State?

Next topic: What Can I Do If the CPU Usage of a Blockchain Node Reaches 100%?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank 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.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.