Downstream clients stop getting block updates periodically

[discoltk]

This has been going on for awhile and continues to be reproducible with Bitcoin Unlimited client connected downstream from bchd.

TCP connection stays up, client is listed by cli agents -- but no block updates are transmitted after a given block.

To reproduce:

Configure BU to have only bchd as upstream block source. Wait about a week, max two weeks. If multiple BU clients are downstream, they stop getting updates at the same height.

[discoltk]

Latest stuck after block 671590

[discoltk]

Stuck again at 673607.

Just to be clear, BCHD is currently crippled as a full node if one desires to have downstream nodes fed by BCHD.

[infertux]

I'm having a similar problem except my downstream client is Fulcrum. I noticed that bchctl getinfo hangs when bchd gets stuck. It looks like bchd is stuck in a loop and stops processing new blocks/requests. I tried increasing the debuglevel but I can't see anything helpful in the logs. Restarting bchd is the only way to "fix" the problem which isn't ideal at all.

[discoltk]

Downstream clients stuck again after 675667

[discoltk]

I'm having a similar problem except my downstream client is Fulcrum. I noticed that bchctl getinfo hangs when bchd gets stuck. It looks like bchd is stuck in a loop and stops processing new blocks/requests. I tried increasing the debuglevel but I can't see anything helpful in the logs. Restarting bchd is the only way to "fix" the problem which isn't ideal at all.

For the issue I'm reporting, bchd does not hang at all.

[discoltk]

In case there is any misunderstanding,

[ internet ] -> [ upstream BU ] -> [ BCHD ] -> [ downstream BU ]

1. Upstream BU processes blocks from the internet without failure.
2. BCHD processes blocks without failure.
3. Downstream updates to BU periodically hangs between block updates. The TCP connection remains up and BCHD reports it as an active client connection. Downstream BU functions such as getinfo do not hang, simply do not progress to current blocks.
4. Restarting downsteam BU resolves the problem (until next time)
5. Configuring downstream BU to receive blocks directly from upstream BU bypasses the problem.

[discoltk]

Stuck again, this time after block 675907