Started up test node @ +/- few seconds Wed Feb 26 15:54:19 CDT 2020. Catching up to max height... 619122 SetBestChain: new best=0000000000000000001159ec899185ec8f056b7655bf7898fef186454efde94f height=619122 work=4041517233816397349951269195 Complete. Now to let the node get a few more than 10 connections, currenly has 9... Done, now has 14 connections. -------------------------------------------------------------------------- In the case of asciilifeform's test with this wedger.py, he said hid didn't perma-wedge, did eventually recover: http://logs.nosuchlabs.com/log/asciilifeform/2020-02-26#1007859 -------------------------------------------------------------------------- Test 1: Send 49999 'getdata for block' commands to the node, see how it reacts and if it recovers. Host, Port, File = 127.0.0.1, 8333, snap_49999.txt mod6@localhost ~ $ ./wedger.py 127.0.0.1 8333 snap_49999.txt Alive: V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=1.2.3.4:8333 Blocks=619122 Sending 1799991-byte message packet... Now listening for replies (Ctl-C to quit...) Violated BTC Protocol: Invalid payload length! mod6@localhost ~ $ .... In the debug.log after all of the request spam: 02/26/20 22:04:07 sending: block Size large: 4295965463 (0x7f282a15e681, 0x7f292a252198) Size wedge: 4295965463 (0x7f282a15e681, 0x7f292a252198) Still wedged minutes later... received getdata for: block 0000000000000000000cffd5f8fff62f3a6c40192f882c686999b93972db3262 02/26/20 22:10:14 sending: block Size large: 4295953404 (0x7f282ab9c175, 0x7f292ac8cd71) Size wedge: 4295953404 (0x7f282ab9c175, 0x7f292ac8cd71) CPU Load @ 1.0. mod6@localhost ~ $ uptime 17:11:08 up 91 days, 6:08, 8 users, load average: 1.00, 0.87, 0.75 mod6@localhost ~ $ free total used free shared buff/cache available Mem: 131935684 4579076 1287076 744 126069532 125905764 Swap: 0 0 0 Also not responding to RPC commands!