“socket sending timeout: 1201s” while doing “verifychain 4 630000” #18995

1. 
   yakitorifoodie commented at 11:30 am on May 17, 2020: none

   Version : Bitcoin Core 0.19.1

   Description : i tried bitcoin-cli verifychain 4 630000 but after some time ( 1201s ) bitcioind log debug.info says socket sending timeout: 1201s. Will it stop verifychain command?

2. yakitorifoodie added the label Bug on May 17, 2020
3. 
   MarcoFalke commented at 12:13 pm on May 17, 2020: member

   Some [1] RPCs might hold cs_main for a long period of time. cs_main may also be needed by the message handling thread (depending on what kind of data the other peer sent you). If it is needed, the thread will wait until the lock can be taken. During that time, no peer’s messages are handled, so they will be disconnected for not sending any data.

   [1]

   At least for flushing the utxoset:

   • dumptxoutset
   • gettxoutsetinfo
   • scantxoutset

   For activating the chain:

   • invalidateblock
   • reconsiderblock

   For walking the chain:

   • verifychain
4. MarcoFalke added the label P2P on May 17, 2020
5. 
   MarcoFalke commented at 12:13 pm on May 17, 2020: member

   Will it stop verifychain command?

   No

6. 
   yakitorifoodie commented at 1:18 pm on May 17, 2020: none

   Thank you for the inputs. Unfortunately bitcoind silently stopped after ~1 hours of verifychain command.

   debug.info log:

   0 Verifying last 630690 blocks at level 4
   1 [0%]...socket sending timeout: 1201s
   2 socket sending timeout: 1201s
   3 socket sending timeout: 1201s
   4 socket sending timeout: 1201s
   5 socket sending timeout: 1201s
   6 socket sending timeout: 1201s
   7 [10%]...[20%]...[30%]...[40%]...[50%]...
   

   after 50% bitcoind stopped with out any log. i’m having sufficient RAM(16G) and CPUs.

7. 
   yakitorifoodie commented at 1:31 pm on May 17, 2020: none

   previously started bitcoind with -dbcache=4000. now trying without dbcache and running verifychain command again.
8. 
   MarcoFalke commented at 1:38 pm on May 17, 2020: member

   verifychain 4 is lacking documentation, but the memory requirements should be O(2*N), where N is the number of blocks to verify
9. 
   yakitorifoodie commented at 2:53 pm on May 17, 2020: none

   even after turning off dbcache bitcoind stopped after [50%].

   bitcoin.conf file

   0rpcuser=user
   1rpcpassword=pass
   2daemon=1
   3txindex=1
   4server=1
   5rpcallowip=0.0.0.0/0
   6rpcport=8332
   

   Unable to resolve it due to lack of documentation. Closing.

10. yakitorifoodie closed this on May 17, 2020

    ---

11. MarcoFalke reopened this on May 17, 2020

    ---

12. 
    MarcoFalke commented at 3:01 pm on May 17, 2020: member

    Unable to resolve it due to lack of documentation. Closing.

    This should be fixed and documented instead.

13. MarcoFalke removed the label Bug on May 17, 2020
14. MarcoFalke added the label Docs on May 17, 2020
15. 
    MarcoFalke commented at 3:04 pm on May 17, 2020: member

    Documentation is here:

    0  -checklevel=<n>
    1       How thorough the block verification of -checkblocks is: level 0 reads
    2       the blocks from disk, level 1 verifies block validity, level 2
    3       verifies undo data, level 3 checks disconnection of tip blocks,
    4       and level 4 tries to reconnect the blocks, each level includes
    5       the checks of the previous levels (0-4, default: 3)
    

    I think this can be copied as is to the RPC help

16. MarcoFalke added the label good first issue on May 17, 2020
17. 
    MarcoFalke commented at 3:13 pm on May 17, 2020: member

    Copy-pasting documentation should be doable as a good first issue.
18. 
    yakitorifoodie commented at 10:45 pm on May 18, 2020: none

    verifychain 4 is lacking documentation, but the memory requirements should be O(2*N), where N is the number of blocks to verify

    Bitcoind not using swapspace after ram is full. How to tell bitcoind to use swapspace. Thank you.

19. 
    syc-xx commented at 11:29 am on June 6, 2020: none

    I’ll work on this issue.
20. 
    MarcoFalke commented at 11:49 am on June 6, 2020: member

    There is already a fix: #19005
21. 
    syc-xx commented at 8:06 pm on June 6, 2020: none

    There is already a fix: #19005

    Ok I’ll pick something else. Thanks.

22. MarcoFalke referenced this in commit 1b90a7b61a on Jun 7, 2020
23. 
    yahiheb commented at 1:22 am on July 31, 2020: contributor

    Should this issue be closed since #19005 was merged?
24. fanquake closed this on Jul 31, 2020

    ---

25. MarcoFalke locked this on Feb 15, 2022

Contributors
yakitorifoodie MarcoFalke syc-xx yahiheb

Labels
Docs P2P good first issue