Bitcoin Core continually status - starting

The logs say their is a problem connecting to RPC service
Could not connect to server 127.0.0.1:8332

electrs also failing to start showing following in the logs
bitcoind RPC polling failed

2024-09-09T12:22:35+01:00 PROCESS TERMINATED BY SIGBUS
2024-09-09T12:22:51+01:00 Error updating blockchain info: error: timeout on transient error: Could not connect to the server 127.0.0.1:8332
2024-09-09T12:22:51+01:00
2024-09-09T12:22:51+01:00 Make sure the bitcoind server is running and that you are connecting to the correct RPC port.
2024-09-09T12:22:51+01:00
2024-09-09T12:22:51+01:00 Error updating network info: error: timeout on transient error: Could not connect to the server 127.0.0.1:8332
2024-09-09T12:22:51+01:00
2024-09-09T12:22:51+01:00 Make sure the bitcoind server is running and that you are connecting to the correct RPC port.

What hardware are you running your Server on?

Are any of your other services stuck in starting or is it just Bitcoin Core? Have you tried restarting the entire Server or just the Bitcoin Core service itself?

You can also try going to Config on your Bitcoin Core Service page & then click Save without changing anything. This should clear it up for you.

There was another case that sounds similar to your that you might want to look at as well.

thanks, just reading through the other thread now

Keep getting these in the OS Logs

ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 135

Whilst Bitcoind logs say

PROCESS TERMINATED BY SIGBUS

Dell optiplex micro 7050
2TB SSD
16 GB RAM

Hi qn33!

I’ve seen this error in OS logs before with another user. They managed to resolve it by replacing the RAM. You can also try running a system rebuild in the System Settings to rebuild the container. If that doesn’t work, try swapping out the RAM and check again.

Ah ok I will try swapping out the RAM. I have already run the system rebuild without any success.

Thanks for the help, appreciate it.

Swapped out the RAM and still get the same issue.