: bvt, don't feel too bad, this is a massive problem owing to the insanity of the gearbox involved. the vast majority of historically observed wedges were never reproduced
: i guess in some quarters this counts for "intrinsic stability" or something, but...
: well, the only thing i feel bad about in this situation is that for some time i was getting wedged in ~30 min, did not check the logs, assumed the DB corruption, rolled back to month-old chain snapshot without keeping the current
: anyone debug.log snapshots of wedge: did the period before wedge involve a large number of continous block requests?
waves a generated-sphere-on-a-bone-that-is-not-a-bone-they-are-idiots
: bvt: Yes, I experience exactly like you describe; right before 'wedge', incoming 30k or so of 'received getdata for: block' in debug.log.
: I have a debug.log that is ~12G that goes back ~3 mos to block #605198, i do see those requests, but in the dozens at a time at most. but not a tidal wave of tens of thousands.
: When alf alerted about this wedge on the 22nd, I was quick to point out this wave of stuff that I don't typicaly see.
: Happy to provide the 12G log if you want that, or a shorter one that shows on 22nd or 23rd my node starting, then getting wedged after wave.
: Apparently main.cpp:ProcessMessage() allows for quite a number of these getdata commands before flagged as 'Misbehaving'. But I've not seen waves like this before now. Quite possible I've just not seen them either tho.
: If others have this same type of behavior, please write in and say, show us the debug.log if you can. Thanks.