KeyMaterial not found in SigningIdentityInfo - blockchain

Question

I am creating a Hyperledger fabric network with 4 node docker swarm node.
I want to create 5 peers, 1 org, 4 orderer, 1 ca.
in node 1. ca, cli, 2 peer(peer0.org1,peer1.org1)
in node 2. 2 orderer 2 peer(peer2.org1,peer3.org1)
in node 3. 2 orderer, 1 peer (peer4.org1)
in node 4. 1 peer (peer5.org1)
When I run docker stack deploy -c docker-compose.yaml hlf.
In manager node 1 peer 2 orderer 1 ca and couchdb are up and running but in other nodes are not. Only couchdb's are runing in other nodes.
When I run docker service logs serviceId. I saw below error.
Cannot run peer because error when setting up MSP of type bccsp from directory /etc/hyperledger/crypto/peer/msp: KeyMaterial not found in SigningIdentityInfo
I created ca msp peers tlsca users files inside org1.example.com in node 1 and copied and pasted to other nodes with same directory.
I couldn't understand what is wrong with this problem. Other peers are same just port and peer number is changed.
peer4org1examplecom:
deploy:
placement:
constraints:
- node.labels.name == worker3
container_name: peer1.org1.example.com
image: hyperledger/fabric-peer:2.1
# extends:
# file: base.yaml
# service: peer-base
environment:
- FABRIC_LOGGING_SPEC=info
- ORDERER_GENERAL_LOGLEVEL=info
- CORE_PEER_LOCALMSPID=Org1MSP
- CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=artifacts_test
- CORE_PEER_ID=peer4.org1.example.com
- CORE_PEER_ADDRESS=peer4.org1.example.com:11051
- CORE_PEER_LISTENADDRESS=0.0.0.0:11051
- CORE_PEER_CHAINCODEADDRESS=peer4.org1.example.com:11052
- CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:11052
# Exposed for discovery Service
- CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer4.org1.example.com:8051
- CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org1.example.com:7051
- CORE_LEDGER_STATE_STATEDATABASE=CouchDB
- CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb4:5984
- CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=
- CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=
- CORE_METRICS_PROVIDER=prometheus
# - CORE_OPERATIONS_LISTENADDRESS=0.0.0.0:9440
- CORE_PEER_TLS_ENABLED=true
- CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/crypto/peer/tls/server.crt
- CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/crypto/peer/tls/server.key
- CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/crypto/peer/tls/ca.crt
- CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/crypto/peer/msp
#extends base.yaml
- CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
- CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=artifacts_default
- CORE_LOGGING_LEVEL=INFO
- CORE_PEER_GOSSIP_USELEADERELECTION=true
- CORE_PEER_GOSSIP_ORGLEADER=false
- CORE_PEER_GOSSIP_SKIPHANDSHAKE=true
ports:
- 11051:9051
volumes:
- /home/ubuntu/hlf-docker-swarm/test-network/artifacts/crypto-config/peerOrganizations/org1.example.com/peers/peer4.org1.example.com/msp:/etc/hyperledger/crypto/peer/msp
- /home/ubuntu/hlf-docker-swarm/test-network/artifacts/crypto-config/peerOrganizations/org1.example.com/peers/peer4.org1.example.com/tls:/etc/hyperledger/crypto/peer/tls
- /var/run/:/host/var/run/
- ./:/etc/hyperledger/
working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
command: peer node start
networks:
test:
aliases:
- peer4.org1.example.com