sawtooth-validator-default sawtooth-validator-default

[liuchao11]

When I use Docker for a Single Sawtooth Node. Follow the steps in website.
In Step 3: Start the Sawtooth Docker Environment:
The problem is below:

sawtooth-settings-tp-default | INFO | sawtooth_sdk::proces | Message: cf7742d809ff457fba0fc06eedc907e2
sawtooth-settings-tp-default | INFO | sawtooth_sdk::proces | sending PingResponse
sawtooth-validator-default | [2023-10-31 03:09:49.534 DEBUG interconnect] No response from 713cce62a68f7672e0ade9a65366537d1387fc01b6fea726893ab30449d76b92f62d207742a703762d9f866d9ea45e97c57061195fea078e28e9241ec2ff5e69 in 10.007903337478638 seconds - beginning heartbeat pings.
sawtooth-validator-default | [2023-10-31 03:09:49.535 DEBUG interconnect] No response from 02744ab3a5235fe142c08ed48ae078e1f91ff11615f09dda419b8b5759e7c449008a4f670648583d6259e7361d9c9a25db4f68a4e2f011bc74da3bb7ab8252ae in 10.007768869400024 seconds - beginning heartbeat pings.
sawtooth-validator-default | [2023-10-31 03:09:49.536 DEBUG interconnect] No response from 010132a6c832702654c52751072ccdf2fd5379befa1f245fcbe4cb25083689bd100e37f7905c56d709308f96c46067a16a0a66f6d094d5fda79505cead42c302 in 10.006694316864014 seconds - beginning heartbeat pings.
sawtooth-intkey-tp-python-default | [2023-10-31 03:09:49.536 DEBUG core] received message of type: PING_REQUEST
sawtooth-xo-tp-python-default | [2023-10-31 03:09:49.537 DEBUG core] received message of type: PING_REQUEST
sawtooth-settings-tp-default | INFO | sawtooth_sdk::proces | Message: c084d9c80c744fa79534ee9c2a5407c0
sawtooth-settings-tp-default | INFO | sawtooth_sdk::proces | sending PingResponse
sawtooth-validator-default | [2023-10-31 03:09:59.540 DEBUG interconnect] No response from 713cce62a68f7672e0ade9a65366537d1387fc01b6fea726893ab30449d76b92f62d207742a703762d9f866d9ea45e97c57061195fea078e28e9241ec2ff5e69 in 10.001838684082031 seconds - beginning heartbeat pings.
sawtooth-validator-default | [2023-10-31 03:09:59.541 DEBUG interconnect] No response from 02744ab3a5235fe142c08ed48ae078e1f91ff11615f09dda419b8b5759e7c449008a4f670648583d6259e7361d9c9a25db4f68a4e2f011bc74da3bb7ab8252ae in 10.00159239768982 seconds - beginning heartbeat pings.
sawtooth-validator-default | [2023-10-31 03:09:59.541 DEBUG interconnect] No response from 010132a6c832702654c52751072ccdf2fd5379befa1f245fcbe4cb25083689bd100e37f7905c56d709308f96c46067a16a0a66f6d094d5fda79505cead42c302 in 10.00166654586792 seconds - beginning heartbeat pings

So, is there any problem with the step before or proxy?

[agunde406]

The heartbeat pings message is not an issue. That debug log is just letting you know that heartbeat pings are being sent to keep the connections alive. If the network is underload, the heartbeat messages are not required.

…

On Mon, Oct 30, 2023 at 10:02 PM liuchao11 ***@***.***> wrote: When I use Docker for a Single Sawtooth Node. Follow the steps in website <https://sawtooth.hyperledger.org/docs/1.2/app_developers_guide/installing_sawtooth.html> . In Step 3: Start the Sawtooth Docker Environment: The problem is below: sawtooth-settings-tp-default | INFO | sawtooth_sdk::proces | Message: bd8dccc6b99d4ad5855651160adf261d sawtooth-settings-tp-default | INFO | sawtooth_sdk::proces | sending PingResponse sawtooth-validator-default | [2023-10-31 02:54:41.614 DEBUG interconnect] No response from c1f3eeaed030584111afa187be97c36f01b3d07cc1d57739ecba003794daf62086b12c5ce1ae6832651e3b563751f589cdc4a12ff5d9893de1e82c547696119f in 10.008634567260742 seconds - beginning heartbeat pings. So, is there any problem with the step before or proxy? — Reply to this email directly, view it on GitHub <#2467>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEK7EPXYNRYE7RELULTQIT3YCBS2XAVCNFSM6AAAAAA6W7SSXGVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE3DSNJUGQ3TGOA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[liuchao11]

@agunde406 Thank you! There is another problem in the step Creating a Sawtooth Test Network.
When I download sawtooth-default-pbft.yaml, then run the step one by one. As I start the Sawtooth network, sawtooth-validator-default-0 container is not running. The wrong code is as below:

sawtooth-validator-default-0 | Generated config-genesis.batch
sawtooth-validator-default-0 | sawtooth.consensus.pbft.members=["0366aac61c18ff2e044e9ce1775fb865b38eb5eee98b78c00287ed37c189dc57f5","02e64eee2926effd634c65ceecf85f46c417ff0e15e8515a863b60c7fb36a59ff0","037b362e1575065e682719712d28eeeef291685726684e435c20de84e68277ab1a","02eb8d8c5d0f6064665f32bdb41fcd1ba216e1c7d85d26d0a460e5d9b088cfc1f4","03c95b24131139e7d82a151214e05d7f1262467fcb30104462ccd23e85b56c1d94"]
sawtooth-validator-default-0 | usage: sawset proposal create [-h] [-k KEY]
sawtooth-validator-default-0 | [-o OUTPUT | --url URL | --sabre-output SABRE_OUTPUT]
sawtooth-validator-default-0 | setting [setting ...]
sawtooth-validator-default-0 | sawset proposal create: error: the following arguments are required: setting
sawtooth-validator-default-0 | bash: line 22: -k: command not found
sawtooth-validator-default-0 | bash: line 23: sawtooth.consensus.algorithm.name=pbft: command not found
sawtooth-validator-default-0 | bash: line 24: sawtooth.consensus.algorithm.version=1.0: command not found
sawtooth-validator-default-0 | bash: line 25: sawtooth.consensus.pbft.members=["0366aac61c18ff2e044e9ce1775fb865b38eb5eee98b78c00287ed37c189dc57f5","02e64eee2926effd634c65ceecf85f46c417ff0e15e8515a863b60c7fb36a59ff0","037b362e1575065e682719712d28eeeef291685726684e435c20de84e68277ab1a","02eb8d8c5d0f6064665f32bdb41fcd1ba216e1c7d85d26d0a460e5d9b088cfc1f4","03c95b24131139e7d82a151214e05d7f1262467fcb30104462ccd23e85b56c1d94"]: command not found
sawtooth-validator-default-0 | bash: line 26: sawtooth.publisher.max_batches_per_block=1200: command not found
sawtooth-validator-default-0 | bash: line 27: -o: command not found
sawtooth-validator-default-0 | bash: line 36: --endpoint: command not found
sawtooth-validator-default-0 | bash: line 37: --bind: command not found
sawtooth-validator-default-0 | bash: line 38: --bind: command not found
sawtooth-validator-default-0 | bash: line 39: --bind: command not found
sawtooth-validator-default-0 | bash: line 40: --scheduler: command not found
sawtooth-validator-default-0 | bash: line 41: --peering: command not found
sawtooth-validator-default-0 | bash: line 42: --maximum-peer-connectivity: command not found