CODEWITHSUNDEEP
hyperledger-fabrichyperledger-composer
priyankasharma55
priyankasharma55

Reputation: 21

Unable to start Fabric on Mac OS, startFabric.sh gives daemon error

I am following the setup as per https://hyperledger.github.io/composer/latest/installing/development-tools.html. But when I run ./startFabric.sh, I run into error as per below logs

docker ps -a:

CONTAINER ID        IMAGE                               COMMAND                  CREATED             STATUS                      PORTS                                        NAMES
53263f6dc18e        hyperledger/fabric-peer:1.2.1       "peer node start"        20 minutes ago      Exited (1) 13 minutes ago                                                peer0.org1.example.com
8e558708b7f6        hyperledger/fabric-orderer:1.2.1    "orderer"                20 minutes ago      Exited (1) 13 minutes ago                                                orderer.example.com
0c373a640583        hyperledger/fabric-couchdb:0.4.10   "tini -- /docker-ent…"   20 minutes ago      Up 13 minutes               4369/tcp, 9100/tcp, 0.0.0.0:5984->5984/tcp   couchdb
e86a4960ab44        hyperledger/fabric-ca:1.2.1         "sh -c 'fabric-ca-se…"   20 minutes ago      Up 13 minutes               0.0.0.0:7054->7054/tcp                       ca.org1.example.com
e30099dbd318        hello-world                         "/hello"                 23 minutes ago      Exited (0) 15 minutes ago                                                hungry_zhukovsky

cd fabric-dev-servers/ && ./startfabric.sh:

Development only script for Hyperledger Fabric control
Running 'startfabric.sh'
FABRIC_VERSION is set to 'hlfv12'
FABRIC_START_TIMEOUT is unset, assuming 15 (seconds)
Stopping couchdb             ... done
Stopping ca.org1.example.com ... done
Removing peer0.org1.example.com ... done
Removing orderer.example.com    ... done
Removing couchdb                ... done
Removing ca.org1.example.com    ... done
Removing network composer_default
Creating network "composer_default" with the default driver
Creating couchdb             ... done
Creating orderer.example.com ... done
Creating ca.org1.example.com    ... done
Creating peer0.org1.example.com ... done
sleeping for 15 seconds to wait for fabric to complete start up
Error response from daemon: Container 
3e81f3aa41969a7ae3f7a09c5c42c16aa55e2527958aef319ad93988ca942f7f is not running

On checking the logs for this container, i see this error :

2019-09-06 09:27:49.868 UTC [msp] getPemMaterialFromDir -> DEBU 020 Reading directory /etc/hyperledger/peer/msp/signcerts
2019-09-06 09:27:49.868 UTC [main] main -> **ERRO 021 Cannot run peer because error when setting up MSP of type bccsp from directory /etc/hyperledger/peer/msp: could not load a valid signer certificate from directory /etc/hyperledger/peer/msp/signcerts: stat /etc/hyperledger/peer/msp/signcerts: no such file or directory**

I get the same error when I try to start the peer container from Kitematic

My setup is as per below:

I found same issue https://github.com/hyperledger/composer/issues/4202 on Windows 10 however I am facing this on Mac OS X 10.11.6.

Upvotes: 2

Views: 317

Answers (2)

Sidhu
Sidhu

Reputation: 1

I had faced similar issue in macOS Sonoma 14.5 and Docker Desktop v4.33.0. The problem was that crypto-config folder is present in /opt/fabric-network folder, for some reason docker is not able to access certs files which are present in non user home directory. I could not find the reason why it is not able to access it.

I moved all the scripts and compose files to my user home i.e ~/fabric-network and now crypto-config folder is present in ~/fabric-network. Then everything worked perfectly.

Upvotes: 0

Narendranath Reddy
Narendranath Reddy

Reputation: 4133

2019-09-06 09:27:49.868 UTC [main] main -> ERRO 021 Cannot run peer because error when setting up MSP of type bccsp from directory /etc/hyperledger/peer/msp: could not load a valid signer certificate from directory /etc/hyperledger/peer/msp/signcerts: stat /etc/hyperledger/peer/msp/signcerts: no such file or directory

It Means running container cannot able to access the mounted certificates folder

Please check volume mount !! in the docker-compose file

Upvotes: 1

Related Questions