Bitcoin Core doesn't pass health check when starting Mempool service

Services Support
1

I recently did a fresh install, everything is working fine. I was notified that updates are available. But since the updates Bitcoin Core is having issues.

My server is running 0.4.0-beta.7 with:

Bitcoin Core 31.0:8

Fulcrum 2.1.0:9

Mempool 3.3.1:1

Tor 0.4.9.5:1

Bitcoin Core is fully synched and starts just fine. I can start Fulcrum, seems to be ok. But as soon as I start Mempool too, Bitcoin Core starts complaining about “stdout maxBuffer length exceeded”.

So everything keeps working as long as I don’t start Mempool.

What can I do? Do I need to down grade to an older version of the services maybe?

1 Like
2

same observation on my server .)

3

Another thread on the same issue:

4

Make 100% sure that you are on the latest versions of StartOS and also all services by hard refreshing the “Updates” page (Ctrl + Shift + R) (CMD + Shift + R on MacOS).

Once everything is on the latest version, this is no longer happening.

5

I am on the latest version of StartOS and also the services, I checked and double checked, but it still happens.

Screenshot 2026-04-29 202747
Screenshot 2026-04-29 2027471626×357 25.7 KB

This screenshot was made just a couple of seconds ago.

6

This happens a few seconds after starting the Mempool service

Screenshot 2026-04-29 202803
Screenshot 2026-04-29 202803563×342 17.8 KB

7

The latest versions as of this very moment for your specific case are:

Bitcoin Core 31.0:9
Fulcrum 2.1.0:10
Mempool 3.3.1:2

These are still only found in the Alpha Marketplace and should only be updated to if you are in current official testing and are fully aware that Alpha versions are only for testing and not for standard everyday use.

They will be released shortly to the main Marketplace when we have made sure everything is working as it should.

8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.