Hi Bobbi,

Thanks again for your response, and for encouraging me to give it a try before coming back hat in hand. Well, here I am. :-)

The root challenge with your response is that I don't know how to do what you are asking to investigate. The way this course is structured, for Lab 1, it is just run a couple of scripts and don't worry about the details. We'll get to those. Well, I ain't got there yet cause I can't get past the last step in start.sh of Lab 1.

So, first I want to respond to your specific comments, then I'll present the detailed output.

Incorrect Certificate Authority (CA) Setup: Make sure that the certificates from the CA for the peers and orderer nodes are correctly configured. If the organization identities aren't correctly recognized by the Fabric network, you might see this type of error.

How do I do that? Since it is all with the generate.sh and start.sh scripts that are provided, I don't know how to know if the nodes are correctly configured. Again, since they are part of the scripts that have been provided, I expect they are OK.

Network not Fully Bootstrapped: Ensure that your Hyperledger Fabric network is fully up and running before you try to execute commands. The peers and the orderer node may not have been fully initialized before the script tried to create and join the channel.

Same comment. How do you tell if the nodes have been fully initialized. I will say that the four containers are set up and appear to be correct, but I don't know how to determine if they have been fully initialized.

Correct CHANNEL_NAME Export: Check if the environment variable CHANNEL_NAME is correctly set. The error message suggests that the channel name is not recognized.

From the output of start.sh below, it appears that allarewelcome is properly named.

Certificate Path: Make sure the --cafile flag points to the correct path of the Orderer's TLS CA certificate file. The ORDERER_TLS_CA environment variable must contain the correct path to the certificate file.

Same comment.

User Identity Configuration: Check if the user MSP (Membership Service Provider) is correctly setup in the core.yaml file. The error message suggests an issue with the creator's identity.

And finally, I can read the core.yaml file, but don't know what to look for to know if it is properly set up. Again, since this was a downloaded file, I'd be surprised if it is in error.

---

Next, here is the complete output. Note that the only modifications to the original start.sh script are: switch from docker-compose to docker compose (which seems to work as it should), and I added
"set -x

trap read debug"

to the top of the script so I could more closely observe what was happening. Here is the output from the script.

fabric@doug-VirtualBox:~/Desktop/lfs272-assets/networkFiles$ ./start.sh

• trap read debug

++ read

• set -ev

Set env vars

export CHANNEL_NAME=allarewelcome

read

++ read

• export CHANNEL_NAME=allarewelcome

• CHANNEL_NAME=allarewelcome

docker compose -f docker-compose.yml down

read

++ read

• docker compose -f docker-compose.yml down

[+] Running 5/5

✔ Container ca.org1.example.com Removed 12.5s

✔ Container cli Removed 3.1s

✔ Container peer0.org1.example.com Removed 2.4s

✔ Container orderer.example.com Removed 1.6s

✔ Network starter_basic Remo... 0.7s

docker compose -f docker-compose.yml up -d ca.org1.example.com orderer.example.com peer0.org1.example.com cli

read

++ read

• docker compose -f docker-compose.yml up -d ca.org1.example.com orderer.example.com peer0.org1.example.com cli

[+] Running 5/5

✔ Network starter_basic Crea... 0.4s

✔ Container orderer.example.com Started 5.7s

✔ Container ca.org1.example.com Started 5.7s

✔ Container peer0.org1.example.com Started 4.9s

✔ Container cli Started 6.4s

Wait for Hyperledger Fabric to start

In case of errors when running later commands, issue export FABRIC_START_TIMEOUT=

export FABRIC_START_TIMEOUT=15

read

++ read

• export FABRIC_START_TIMEOUT=15

• FABRIC_START_TIMEOUT=15

sleep ${FABRIC_START_TIMEOUT}

read

++ read

• sleep 15

Create the application channel

ORDERER_TLS_CA=docker exec cli env | grep ORDERER_TLS_CA | cut -d'=' -f2

read

++ read

++ docker exec cli env

++ grep ORDERER_TLS_CA

++ cut -d= -f2

• ORDERER_TLS_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

docker exec cli peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f /etc/hyperledger/configtx/$CHANNEL_NAME.tx --tls --cafile $ORDERER_TLS_CA

read

++ read

• docker exec cli peer channel create -o orderer.example.com:7050 -c allarewelcome -f /etc/hyperledger/configtx/allarewelcome.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

2023-08-15 22:31:00.532 UTC 0001 INFO [channelCmd] InitCmdFactory -> Endorser and orderer connections initialized

2023-08-15 22:31:00.578 UTC 0002 INFO [cli.common] readBlock -> Expect block, but got status: &{NOT_FOUND}

2023-08-15 22:31:00.584 UTC 0003 INFO [channelCmd] InitCmdFactory -> Endorser and orderer connections initialized

2023-08-15 22:31:01.086 UTC 0004 INFO [cli.common] readBlock -> Expect block, but got status: &{SERVICE_UNAVAILABLE}

2023-08-15 22:31:01.102 UTC 0005 INFO [channelCmd] InitCmdFactory -> Endorser and orderer connections initialized

2023-08-15 22:31:01.304 UTC 0006 INFO [cli.common] readBlock -> Expect block, but got status: &{SERVICE_UNAVAILABLE}

2023-08-15 22:31:01.310 UTC 0007 INFO [channelCmd] InitCmdFactory -> Endorser and orderer connections initialized

2023-08-15 22:31:01.514 UTC 0008 INFO [cli.common] readBlock -> Expect block, but got status: &{SERVICE_UNAVAILABLE}

2023-08-15 22:31:01.520 UTC 0009 INFO [channelCmd] InitCmdFactory -> Endorser and orderer connections initialized

2023-08-15 22:31:01.724 UTC 000a INFO [cli.common] readBlock -> Expect block, but got status: &{SERVICE_UNAVAILABLE}

2023-08-15 22:31:01.737 UTC 000b INFO [channelCmd] InitCmdFactory -> Endorser and orderer connections initialized

2023-08-15 22:31:01.942 UTC 000c INFO [cli.common] readBlock -> Expect block, but got status: &{SERVICE_UNAVAILABLE}

2023-08-15 22:31:01.950 UTC 000d INFO [channelCmd] InitCmdFactory -> Endorser and orderer connections initialized

2023-08-15 22:31:02.157 UTC 000e INFO [cli.common] readBlock -> Received block: 0

Join peer0.org1.example.com to the channel

docker exec cli peer channel join -b $CHANNEL_NAME.block

read

++ read

• docker exec cli peer channel join -b allarewelcome.block

2023-08-15 22:31:07.111 UTC 0001 INFO [channelCmd] InitCmdFactory -> Endorser and orderer connections initialized

Error: proposal failed (err: rpc error: code = Unknown desc = error validating proposal: access denied: channel [] creator org unknown, creator is malformed)

fabric@doug-VirtualBox:~/D

So, that's all I have. If you need something additional, I can't imagine what it would be since all I did was execute the two scripts that are provided as a part of Lab 1.

Really looking forward to getting past this so I can start learning the details of this wonderful set of products.

Thanks in advance for your guidance.

Doug