RPC stdout maxBuffer length exceeded Bitcoin knots 29.3.5

After I did all the updates today, my bitcoin knots health check now says “RPC stdout maxBuffer length exceeded”. I believe this happens once I connect at least 4 of the services to it. No idea how to fix.

I am on the latest 0.4.0 beta

I got the same thing on core 31.0:8, also on the latest 0.4.0-beta.6. If I turn off mempool (3.3.1:1) and fulcrum (2.1.0:9) and restart core, it goes away. I can restart fulcrum and it’s fine, but if I try to restart mempool it comes back.

Make sure you are running the latest Beta 6 version of StartOS 040 as well as having all services up to their latest versions.

Everything is as updated as it can be.

mine as well. that is what caused the issue

Hey, same here .) Im on beta 7 with bitcoin core, all services updated. I can see xx lines of “Health Check bitcoind failed: stdout maxBuffer lenght exceeded” in my logs and after some time it goes back to normal. But it looks like just health check issue, because it keeps its peers connected and overall looks like running just fine.

mempool appears to be the trigger that causes this issue

Updated to beta.7. Still have issue.

1 Like

same. still happens even when i leave mempool stopped as well

trying to use my core node alone with only bitcoin and tor running causes the same issue