[ESPINS Fork] Is my server stuck? Or should I just let it go to proceed

I’m new to creditcoin mining.
I followed official mining docs but I think the server is stuck somewhere.
The server doesn’t go any further.
Here’s the info when I turn the server on.
Should I have to wait to proceed?

Creating network “server_default” with the default driver
Creating sawtooth-validator-default …
Creating creditcoin-gateway …
Creating sawtooth-validator-default
Creating sawtooth-validator-default … done
Creating sawtooth-rest-api-default …
Creating sawtooth-settings-tp-default …
Creating sawtooth-settings-tp-default
Creating sawtooth-settings-tp-default … done
Creating creditcoin-processor …
Creating creditcoin-processor … done
Attaching to creditcoin-gateway, sawtooth-validator-default, sawtooth-settings-tp-default, sawtooth-rest-api-default, creditcoin-processor
sawtooth-validator-default | [2021-10-13 06:33:58.797 WARNING cli] Network key pair is not configured, Network communications between validators will not be authenticated or encrypted.
creditcoin-processor | Connecting to tcp://validator:4004
creditcoin-processor | Using gateway URL: tcp://gateway:55555
creditcoin-processor | 1 [0x7f846b24d780] DEBUG sawtooth.TransactionProcessor null - signal handler initialized
creditcoin-processor | 1 [0x7f846b24d780] DEBUG sawtooth.TransactionProcessor null - TransactionProcessor::RegisterHandler
creditcoin-processor | Running
creditcoin-processor | 1 [0x7f846b24d780] DEBUG sawtooth.TransactionProcessor null - Connect to inproc://request_queue
creditcoin-processor | 1 [0x7f846b24d780] INFO sawtooth.TransactionProcessor null - Connect to: tcp://validator:4004
creditcoin-processor | 1 [0x7f846b24d780] INFO sawtooth.MessageDispatcher null - Connecting to tcp://validator:4004
creditcoin-processor | 2 [0x7f8465f75700] INFO sawtooth.MessageDispatcher null - Server connection state changed to: CONNECTED
creditcoin-processor | 2 [0x7f846b24d780] INFO sawtooth.TransactionProcessor null - TransactionProcessor::Run : Server connected
creditcoin-processor | 2 [0x7f846b24d780] DEBUG sawtooth.TransactionProcessor null - TransactionProcessor::Register: CREDITCOIN
creditcoin-processor | 2 [0x7f846b24d780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.0
creditcoin-processor | 4 [0x7f8465f75700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
creditcoin-processor | 4 [0x7f846b24d780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.1
creditcoin-processor | 5 [0x7f8465f75700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
creditcoin-processor | 5 [0x7f846b24d780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.2
creditcoin-processor | 7 [0x7f8465f75700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
creditcoin-processor | 7 [0x7f846b24d780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.3
creditcoin-processor | 8 [0x7f8465f75700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
creditcoin-processor | 8 [0x7f846b24d780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.4
creditcoin-processor | 9 [0x7f8465f75700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
creditcoin-processor | 9 [0x7f846b24d780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.5
creditcoin-processor | 10 [0x7f8465f75700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
creditcoin-processor | 10 [0x7f846b24d780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.6
creditcoin-processor | 11 [0x7f8465f75700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
creditcoin-processor | 11 [0x7f846b24d780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.7
creditcoin-processor | 12 [0x7f8465f75700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 5
creditcoin-processor | 12 [0x7f8465f75700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
creditcoin-processor | Applicator::Apply
creditcoin-processor | 14 [0x7f8465f75700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 8
creditcoin-processor | 6007 [0x7f8465f75700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 117

I don’t see any issues with the above logs. If you want more detail, you could change this line under the validator section in your docker-compose.yaml file from:

            sawtooth-validator \

to:

            sawtooth-validator -vv \

This will enable more verbose logging on the Validator

Now, 22 hours have passed since I wrote this post.
After waiting longer, the above log was confirmed to be normal.
I can see the server’s block height is going up:

[Server] 932963 [Network] 957609 [Peer] 5

It seems that I have to wait more time to mine blocks.
Is this the usual thing to wait for the current network block to be reached?

Here’s the progress ongoing.
The server had reached the latest block and it did something.
But there are mysterious things that I can’t understand in the latest logs.

Block 959156 has been already mined but the server started validating the block and then stuck. The server does not output any logs to the terminal after finishing the validation of block 959156. Furthermore, The block was already dropped before as you can see in the logs below.
What is happening in there? And there are error logs that the connection was refused. see “[Errno 111] Connection refused”
I’m using a multi-threading mining script that someone had posted in this community

[2021-10-15 07:33:36.373 DEBUG signature_verifier] Drop already validated block: 467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9
[2021-10-15 07:33:36.374 DEBUG signature_verifier] Drop already validated block: 467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9
[2021-10-15 07:33:36.375 DEBUG signature_verifier] Drop already validated block: 467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9
[2021-10-15 07:33:36.379 DEBUG completer] Drop duplicate block: 467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9 (block_num:959156, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:177d2cf1148c666f284fdf836d334a98ce7df161b5d50fa95f05146d7a17fcb00385b86864997d18a72208209db7380571cd3de20a2e044dc8ead7c808b99c12)
[2021-10-15 07:33:36.379 DEBUG chain] Block received: 467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9 (block_num:959156, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:177d2cf1148c666f284fdf836d334a98ce7df161b5d50fa95f05146d7a17fcb00385b86864997d18a72208209db7380571cd3de20a2e044dc8ead7c808b99c12)
[2021-10-15 07:33:36.380 INFO block_validator] Starting block validation of : 467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9 (block_num:959156, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:177d2cf1148c666f284fdf836d334a98ce7df161b5d50fa95f05146d7a17fcb00385b86864997d18a72208209db7380571cd3de20a2e044dc8ead7c808b99c12)
1948619 [0x7fbfd00d4700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 5
Applicator::Apply
1948621 [0x7fbfd00d4700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 8
[2021-10-15 07:33:36.689 INFO block_validator] Comparing current chain head ‘177d2cf1148c666f284fdf836d334a98ce7df161b5d50fa95f05146d7a17fcb00385b86864997d18a72208209db7380571cd3de20a2e044dc8ead7c808b99c12 (block_num:959155, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:a31ba2de864fa86c81acd59fb891713b6893c00027ab24fcd9ddd7307c8ebfaf3e9b9360560b797212ff7ce0f044e53e0843d2cf967844a6a73e236d76cca450)’ against new block ‘177d2cf1148c666f284fdf836d334a98ce7df161b5d50fa95f05146d7a17fcb00385b86864997d18a72208209db7380571cd3de20a2e044dc8ead7c808b99c12 (block_num:959155, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:a31ba2de864fa86c81acd59fb891713b6893c00027ab24fcd9ddd7307c8ebfaf3e9b9360560b797212ff7ce0f044e53e0843d2cf967844a6a73e236d76cca450)’
[2021-10-15 07:33:36.690 INFO block_validator] Fork comparison at height 959156 is between - and 467d87d0
[2021-10-15 07:33:36.690 INFO chain] Chain head updated to: 467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9 (block_num:959156, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:177d2cf1148c666f284fdf836d334a98ce7df161b5d50fa95f05146d7a17fcb00385b86864997d18a72208209db7380571cd3de20a2e044dc8ead7c808b99c12)
[2021-10-15 07:33:36.690 INFO publisher] Now building on top of block: 467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9 (block_num:959156, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:177d2cf1148c666f284fdf836d334a98ce7df161b5d50fa95f05146d7a17fcb00385b86864997d18a72208209db7380571cd3de20a2e044dc8ead7c808b99c12)
[2021-10-15 07:33:36.690 DEBUG init] on cancel publish block POW
[2021-10-15 07:33:36.690 DEBUG init] Stop call SOLVER_PRIM
[2021-10-15 07:33:36.690 DEBUG init] Stop call SOLVER_PERF
[2021-10-15 07:33:36.692 DEBUG publisher] Loaded batch injectors: [<sawtooth_validator.journal.batch_injector.GluwaBatchInjector object at 0x7c04a0482cf8>]
[2021-10-15 07:33:36.693 DEBUG init] Start solver call SOLVER_PRIM
[2021-10-15 07:33:36.693 INFO init] New block using Gluwa PoW 1.1 consensus
[Errno 111] Connection refused
[2021-10-15 07:33:36.694 DEBUG chain] Verify descendant blocks: 467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9 (block_num:959156, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:177d2cf1148c666f284fdf836d334a98ce7df161b5d50fa95f05146d7a17fcb00385b86864997d18a72208209db7380571cd3de20a2e044dc8ead7c808b99c12) ([])
1948629 [0x7fbfd00d4700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 5
Applicator::Apply
1948630 [0x7fbfd00d4700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 8
[2021-10-15 07:33:36.778 INFO block_validator] Finished block validation of: 467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9 (block_num:959156, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:177d2cf1148c666f284fdf836d334a98ce7df161b5d50fa95f05146d7a17fcb00385b86864997d18a72208209db7380571cd3de20a2e044dc8ead7c808b99c12)

And I got these newer logs after 15 mins passed.

[2021-10-15 07:50:19.448 DEBUG completer] Drop duplicate block: 57a73bd9dc32cc60103a7a2ab63143d96c18a16f7c1432979d523d5ccd9a3b335792919036c4afc657fe3d9dd4875fdb778f1b5d49b88d32f502117903de61ad (block_num:959157, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9)
[2021-10-15 07:50:19.449 DEBUG chain] Block received: 57a73bd9dc32cc60103a7a2ab63143d96c18a16f7c1432979d523d5ccd9a3b335792919036c4afc657fe3d9dd4875fdb778f1b5d49b88d32f502117903de61ad (block_num:959157, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9)
[2021-10-15 07:50:19.450 INFO block_validator] Starting block validation of : 57a73bd9dc32cc60103a7a2ab63143d96c18a16f7c1432979d523d5ccd9a3b335792919036c4afc657fe3d9dd4875fdb778f1b5d49b88d32f502117903de61ad (block_num:959157, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9)
2951421 [0x7fbfd00d4700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 5
Applicator::Apply
2951422 [0x7fbfd00d4700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 8
[2021-10-15 07:50:19.490 INFO block_validator] Comparing current chain head ‘467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9 (block_num:959156, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:177d2cf1148c666f284fdf836d334a98ce7df161b5d50fa95f05146d7a17fcb00385b86864997d18a72208209db7380571cd3de20a2e044dc8ead7c808b99c12)’ against new block ‘467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9 (block_num:959156, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:177d2cf1148c666f284fdf836d334a98ce7df161b5d50fa95f05146d7a17fcb00385b86864997d18a72208209db7380571cd3de20a2e044dc8ead7c808b99c12)’
[2021-10-15 07:50:19.491 INFO block_validator] Fork comparison at height 959157 is between - and 57a73bd9
[2021-10-15 07:50:19.491 INFO chain] Chain head updated to: 57a73bd9dc32cc60103a7a2ab63143d96c18a16f7c1432979d523d5ccd9a3b335792919036c4afc657fe3d9dd4875fdb778f1b5d49b88d32f502117903de61ad (block_num:959157, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9)
[2021-10-15 07:50:19.491 INFO publisher] Now building on top of block: 57a73bd9dc32cc60103a7a2ab63143d96c18a16f7c1432979d523d5ccd9a3b335792919036c4afc657fe3d9dd4875fdb778f1b5d49b88d32f502117903de61ad (block_num:959157, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9)
[2021-10-15 07:50:19.491 DEBUG init] on cancel publish block POW
[2021-10-15 07:50:19.491 DEBUG init] Stop call SOLVER_PRIM
[2021-10-15 07:50:19.491 DEBUG init] Stop call SOLVER_PERF
[2021-10-15 07:50:19.493 DEBUG publisher] Loaded batch injectors: [<sawtooth_validator.journal.batch_injector.GluwaBatchInjector object at 0x7c04a0583550>]
[2021-10-15 07:50:19.494 DEBUG init] Start solver call SOLVER_PRIM
[2021-10-15 07:50:19.494 INFO init] New block using Gluwa PoW 1.1 consensus
[Errno 111] Connection refused
[2021-10-15 07:50:19.495 DEBUG chain] Verify descendant blocks: 57a73bd9dc32cc60103a7a2ab63143d96c18a16f7c1432979d523d5ccd9a3b335792919036c4afc657fe3d9dd4875fdb778f1b5d49b88d32f502117903de61ad (block_num:959157, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9) ([])
2951429 [0x7fbfd00d4700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 5
Applicator::Apply
2951431 [0x7fbfd00d4700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 8
[2021-10-15 07:50:19.535 INFO block_validator] Finished block validation of: 57a73bd9dc32cc60103a7a2ab63143d96c18a16f7c1432979d523d5ccd9a3b335792919036c4afc657fe3d9dd4875fdb778f1b5d49b88d32f502117903de61ad (block_num:959157, state:c0c57e29a6b48f38b94e56a5fb3469fae5e2c7999cb7842b80af8bf8bbae2660, previous_block_id:467d87d006d37e1b9a2eaeea17d8ecc16457bbd3c9729f2b38d21b710c2427af6c75aee90b63447dcdd10c70c3ff0a90c4d708685993d60ac453c95a439300f9)

“[Errno 111] Connection refused”

Is hashServer running properly?

Did you check that hashServer was compiled properly?

Yes, I have verified that the hash server is working.
See log below. I copied it from hashServer.log file.


WORK,c7243779be950f8ac5ce35bda3fe9ea352…
WORK,7766099d40cd260b1140640c9959e071db…

For now, I am using the original “gluwa version” and compared it to the “ESPINS FORK version”.
These are the recent logs I got from the gluwa version.
The two versions of the logs don’t seem to be very different.
I just want to know if these logs are saying it’s an error or not.
The logs are always saying “Drop already validated block.”

9eb310a1317be236024f4ff75424d3da5300c7405f2799b955784f2bc474dd47a81007e156108c26a7
[2021-10-18 07:33:02.253 DEBUG signature_verifier] Drop already validated block: c4d207d49b0cbf03cbbd24262815fa736c745c8da34d2a9eb310a1317be236024f4ff75424d3da5300c7405f2799b955784f2bc474dd47a81007e156108c26a7
13032195 [0x7f180f7fe700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 5
Applicator::Apply
[2021-10-18 07:33:02.269 DEBUG signature_verifier] Drop already validated block: dda3e4e5cd9313cb6a8e10caca7d1b09bab5626dc7b2d76361e0af3b27a93a2f73d1bf4adb1926d1f799e8ccefe15e4a0e44db96108f10fbf4237792567b2128
13032199 [0x7f180f7fe700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 8
[2021-10-18 07:33:02.273 INFO block_validator] Comparing current chain head ‘790daa10061ff258de81c4fcb268d221bc4e62c49560f1ce914d499f8224282e7cabb4c480bb58cc43a6b8db655ec428d9311b507c6b1053c5e05d5592392e63 (block_num:963280, state:d6bc1442f5cf8dd439d6677e24771266a64421942acae9b1b773199f938b92ea, previous_block_id:249951fd76df9e2e9b6a31734af4a04566a222a379ac5e2d754408b64f008e4b77d2f41550554c424cdd1f0c78d6cf2844f09fd172b277d263917a15edbb773c)’ against new block ‘790daa10061ff258de81c4fcb268d221bc4e62c49560f1ce914d499f8224282e7cabb4c480bb58cc43a6b8db655ec428d9311b507c6b1053c5e05d5592392e63 (block_num:963280, state:d6bc1442f5cf8dd439d6677e24771266a64421942acae9b1b773199f938b92ea, previous_block_id:249951fd76df9e2e9b6a31734af4a04566a222a379ac5e2d754408b64f008e4b77d2f41550554c424cdd1f0c78d6cf2844f09fd172b277d263917a15edbb773c)’
[2021-10-18 07:33:02.273 INFO block_validator] Fork comparison at height 963281 is between - and d4e5116a
[2021-10-18 07:33:02.273 INFO chain] Chain head updated to: d4e5116a472b24d159ae3e327ad0735c6a3acf0ef84aa18f596c3701ea0513520d80bf8398bd2085766fc1fcf6e2aeca6334719a921685bca55f64041b4e0f63 (block_num:963281, state:d6bc1442f5cf8dd439d6677e24771266a64421942acae9b1b773199f938b92ea, previous_block_id:790daa10061ff258de81c4fcb268d221bc4e62c49560f1ce914d499f8224282e7cabb4c480bb58cc43a6b8db655ec428d9311b507c6b1053c5e05d5592392e63)
[2021-10-18 07:33:02.273 INFO publisher] Now building on top of block: d4e5116a472b24d159ae3e327ad0735c6a3acf0ef84aa18f596c3701ea0513520d80bf8398bd2085766fc1fcf6e2aeca6334719a921685bca55f64041b4e0f63 (block_num:963281, state:d6bc1442f5cf8dd439d6677e24771266a64421942acae9b1b773199f938b92ea, previous_block_id:790daa10061ff258de81c4fcb268d221bc4e62c49560f1ce914d499f8224282e7cabb4c480bb58cc43a6b8db655ec428d9311b507c6b1053c5e05d5592392e63)
[2021-10-18 07:33:02.273 DEBUG init] on cancel publish block POW
[2021-10-18 07:33:02.274 DEBUG init] Stop call SOLVER_PRIM
[2021-10-18 07:33:02.274 DEBUG init] Stop call SOLVER_PERF
[2021-10-18 07:33:02.275 DEBUG publisher] Loaded batch injectors: [<sawtooth_validator.journal.batch_injector.GluwaBatchInjector object at 0x7c0de44c5f60>]
[2021-10-18 07:33:02.276 DEBUG init] Start solver call SOLVER_PRIM
[2021-10-18 07:33:02.276 INFO init] New block using Gluwa PoW 1.1 consensus
[2021-10-18 07:33:02.277 DEBUG chain] Verify descendant blocks: d4e5116a472b24d159ae3e327ad0735c6a3acf0ef84aa18f596c3701ea0513520d80bf8398bd2085766fc1fcf6e2aeca6334719a921685bca55f64041b4e0f63 (block_num:963281, state:d6bc1442f5cf8dd439d6677e24771266a64421942acae9b1b773199f938b92ea, previous_block_id:790daa10061ff258de81c4fcb268d221bc4e62c49560f1ce914d499f8224282e7cabb4c480bb58cc43a6b8db655ec428d9311b507c6b1053c5e05d5592392e63) ([])
13032206 [0x7f180f7fe700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 5
Applicator::Apply
13032208 [0x7f180f7fe700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 8
[2021-10-18 07:33:02.330 INFO block_validator] Finished block validation of: d4e5116a472b24d159ae3e327ad0735c6a3acf0ef84aa18f596c3701ea0513520d80bf8398bd2085766fc1fcf6e2aeca6334719a921685bca55f64041b4e0f63 (block_num:963281, state:d6bc1442f5cf8dd439d6677e24771266a64421942acae9b1b773199f938b92ea, previous_block_id:790daa10061ff258de81c4fcb268d221bc4e62c49560f1ce914d499f8224282e7cabb4c480bb58cc43a6b8db655ec428d9311b507c6b1053c5e05d5592392e63)
[2021-10-18 07:33:02.332 DEBUG signature_verifier] Drop already validated block: dda3e4e5cd9313cb6a8e10caca7d1b09bab5626dc7b2d76361e0af3b27a93a2f73d1bf4adb1926d1f799e8ccefe15e4a0e44db96108f10fbf4237792567b2128
[2021-10-18 07:33:02.333 DEBUG responder] Block e64b5292f710c1e6f64e645a803ab690a53e255e6ef030d2b23851c74935338e76c7fee628d799cf951b76cbdfde031c8ec3be5afc5b034bf7f6b6425773d4a6 has already been requested
[2021-10-18 07:33:02.337 DEBUG signature_verifier] Drop already validated block: 46d851cf0a9e0a1f7c5c3f0b0cc5dd0dc1c9deeda41c53d37ee8628c548a0fa920bd7480a4f38a8665bc9b2cb7892085e730e33fda07cb5f06c712b9573d04a8

Have tried with uploaded snapshot? If you tried first block of network. It will take quite long time to reach current network’s block level.

Yes, I started with the uploaded snapshot. By the way, the snapshot’s size is quite big.