Topics

Trace and Trace issue


Prem Baranwal
 

Hi, Has anyone recently been able to set up the grid/grid-contrib and run the asset-client successfully? Does it require any changes in the docker-compose.yaml?
I tried to run the asset-client example as per the instructions at https://github.com/hyperledger/grid-contrib/tree/master/track_and_trace and run into the following error -
Grid-TnTError.png
At this point there were already 12 blocks created. Later, I tried a couple of things like changing the hyperledger/sawtooth docker images to chime (1.2.5) and adding dependency of sabre-tp to *-contract-builder services. But that led to some validator connection error - Failed to receive events; aborting: connection received invalid message: Received unexpected message: PING_REQUEST.

Any help will be appreciated.

Prem Baranwal


Peter Schwarz
 

Hi Prem,

Looking at the particular error there, you want to make sure that you've updated both the validator and the devmode consensus engines to the 1.2 release branch.

Cheers,

Peter


On Mon, Jul 20, 2020 at 4:38 AM Prem Baranwal <prem.baranwal@...> wrote:
Hi, Has anyone recently been able to set up the grid/grid-contrib and run the asset-client successfully? Does it require any changes in the docker-compose.yaml?
I tried to run the asset-client example as per the instructions at https://github.com/hyperledger/grid-contrib/tree/master/track_and_trace and run into the following error -
Grid-TnTError.png
At this point there were already 12 blocks created. Later, I tried a couple of things like changing the hyperledger/sawtooth docker images to chime (1.2.5) and adding dependency of sabre-tp to *-contract-builder services. But that led to some validator connection error - Failed to receive events; aborting: connection received invalid message: Received unexpected message: PING_REQUEST.

Any help will be appreciated.

Prem Baranwal


Prem Baranwal
 

Thanks Peter.
Do you mean changing the tag in docker-compose.yaml from 1.1 to 1.2.5 for all the hyperledger images? The highest version matching 1.2.* published on docker hub for sawtooth-validator is 1.2.5.
validator:
  image: hyperledger/sawtooth-validator:1.1
 to 
validator:
  image: hyperledger/sawtooth-validator:1.2.5

I actually tried to change it to chime tag which is essentially same as 1.2.5. That resolved the consensus error and i was able to execute the intkey TP transactions But it gave the following validator connection error when i submitted the get-started user form from aseet_client UI Failed to receive events; aborting: connection received invalid message: Received unexpected message: PING_REQUEST.


Prem Baranwal
 

Attaching the screenshot of the error i got after updating the docker images to 1.2