Bool Network
  • Introduction
    • What is Bool Network
    • Key features and benefits
    • Roadmap and Milestones
  • INTEROPERABILITY PROTOCOL
    • Overview
    • Architecture
    • Dynamic Hidden Committee (DHC)
      • Security trust flow
      • Lifecycle
      • Messaging Layer
    • Self Custody
      • Channels
      • Workflow
      • Escape Hatch
  • USER GUIDE
    • Beta Testnet
      • Getting Started
      • Network Information
      • Wallet Setup
      • Token Faucet
      • DHC Update
      • Node Server
        • Recommend List
        • Purchase Guide
      • Node Setup
        • DHC Node Setup
          • Local LAN Configuration for SGX
          • Run a chain via snapshot
        • Case Study
      • Node Management
        • For DHC Voter
        • For DHC Owner
  • EVM Ecosystem
    • Getting Started
      • Arbitrary Message Transmission
    • AMT Bridges
      • Network configuration
      • Create committees
      • Build a bridge
      • Bind Consumer to Anchor
      • Other operations
    • Smart Contracts
      • Primary Contracts
        • AnchorFactory
        • Messenger
        • Interfaces
          • IAnchorFactory
          • IMessenger
      • On-chain endpoint: Anchor
        • Anchor.sol
        • IAnchor.sol
      • BoolConsumerBase
        • BoolConsumerBase.sol
        • IBoolConsumerBase.sol
    • User Configurations
    • Application Examples
      • HelloWeb3.sol
    • Technical Reference
      • Chain IDs
      • Deployment Addresses
        • Devnet
        • Testnet
        • Alpha Mainnet
      • Faucet
  • Applications
    • B² Bool Bridge
      • B² Bool Bridge (Particle)
      • B² Bool Bridge (MetaMask)
    • Bool Swap
      • Pool Configuration
      • Deployment Addresses
        • Alpha Mainnet
  • Develop guide
    • Network Configuration
    • System Configuration
    • Testnet
      • Bool Chain
        • Node operators
        • Validators
      • DHC Nodes
        • Prerequisites
        • Quick Start
  • Advanced Tutorials
    • Token Bridge
  • Community and Support
    • Media Kit
    • FAQ
  • Official Links
    • GitHub
    • Twitter
    • Telegram
    • Discord
    • Youtube
    • Medium
Powered by GitBook
On this page
  • Case 1
  • Case 2
  • Case 3
  • Case 4
  • Case 5
  • Case 6
  • Case 7
  • Case 8
  • Case9
  • Case 10
  1. USER GUIDE
  2. Beta Testnet
  3. Node Setup

Case Study

PreviousRun a chain via snapshotNextNode Management

Last updated 6 months ago

Case 1

git clone https://github.com/occlum/enable_rdfsbase.git
cd enable_rdfsbase 
make && make install  #if still error，remake && reinstall

Case 2

  • Mirror is incorrect.

  • Curl is not installed in the container.

Case 3

  • Install curl within the container.

  • Missing sgx_default_gcnl.conf or sgx_default_qcnl.conf file

Case 4

  • Mirror version is not correct, please check the mirror ID.

  • Wrong version

Case 5

Mirroring is wrong, this time apply epid mirroring on Azure.

Case 6

Configuration file error, private key length is not correct.

Case 7

Check current configuration of max_map_count:

cat /proc/sys/vm/max_map_count

Not persistent way to modify the max_map_count:

sysctl -w vm.max_map_count=3097152

To make the changes persistent you should modify /etc/sysctl.conf and then (optionally) execute sysctl -p to apply the changes without reboot

echo "vm.max_map_count=3097152" >> /etc/sysctl.conf
sysctl -p

Case 8

If you are using the v0.11.9 image version of DHC, the Linux kernel version of the Operating System must be greater than 6.2. Another option is to reinstall the operating system, using at least 22.04 Ubuntu version.

Case9

If the "current peers" is 0, it means your device can not be connected through the P2P network. You should check the internet connection and the public IP first. Then you should check the security configuration of the cloud service which you can refer to the official docs for help.

Case 10

For images with versions greater than v0.12.8, you need to add the run command to the startup command line, for example occlum run /bin/bnk-watcher run /host/keyring.toml.