How to troubleshoot the Orderer peer? The Docker container terminated by itself.

You can follow this tutorial to troubleshoot the Orderer peer.

1. Check the log file of the Orderer peer:

$ docker logs --tail 10 orderer.example.com
[localconfig] completeInitialization -> INFO 001 Kafka.Version unset, setting to 0.10.2.0
[orderer.common.server] initializeLocalMsp -> FATA 002 Failed to initialize local MSP: \
   could not load a valid signer certificate from directory \
   /var/hyperledger/orderer/msp/signcerts: stat \
   /var/hyperledger/orderer/msp/signcerts: no such file or directory

2. Check for the missing directory, signcerts:

$ cd fabric-orderer

$ ls -l msp
drwxr-xr-x 2 fyicenter 4096 Apr  1 21:12 admincerts
drwxr-xr-x 2 fyicenter 4096 Apr  1 21:12 cacerts
drwxr-xr-x 2 fyicenter 4096 Apr  1 21:12 tlscacerts

3. Copy the MSP entry from the BYFN tutorials again:

$ cp -r ~/hyperledger-binaries/fabric-samples/first-network/crypto-config\
   /ordererOrganizations/example.com/orderers/orderer.example.com/msp/ .

$ ls -l msp
drwxr-xr-x 2 fyicenter 4096 Apr  1 03:15 admincerts
drwxr-xr-x 2 fyicenter 4096 Apr  1 03:15 cacerts
drwxr-xr-x 2 fyicenter 4096 Apr  1 03:15 keystore
drwxr-xr-x 2 fyicenter 4096 Apr  1 03:15 signcerts
drwxr-xr-x 2 fyicenter 4096 Apr  1 03:15 tlscacerts

4. Run "docker-compose" command again:

$ docker-compose -f docker-compose-orderer.yaml up -d --no-deps
Creating network "fabric-orderer_hello" with the default driver
Creating volume "fabric-orderer_orderer.example.com" with default driver
Creating orderer.example.com ... done

$ docker ps
IMAGE                                    STATUS         NAMES
hyperledger/fabric-orderer:amd64-1.4.0   Up 3 minutes   orderer.example.com

As you can see, the Orderer peer is running fine now.

 

⇒ Default orderer.yaml in Orderer Docker Image

⇐ "docker-compose" - Deploy Orderer to Docker

⇑ Setting Up Orderer Peer Manually

⇑⇑ Hyperledger Tutorials