reply on: Start9 Bitcoin Core Issue \ stacker news ~bitcoin

pull down to refresh

41 sats \ 10 replies \ @nym 8 Jan \ parent \ on: Start9 Bitcoin Core Issue bitcoin_support

Not a bad idea. Sometimes it is easier to start fresh anyway.

Usually not necessary if you aren't running MICROS~1 software.

Last time this happened I spent days on forums, reading guides, etc, with no clear-cut answers. I did discover that I'm not the only one experiencing the issue.

51 sats \ 7 replies \ @DarthCoin 8 Jan

Like nym said, first thing you need to look into logs. Both bitcoin and electrs. Sometimes bitcoin take long time to catch up the blocks and indexes from the moment you stop it to update. Electrs is waiting for bitcoin to finish and then it start its own index that also can take for a while. Meanwhile all other dependent services like LN node are just waiting.

Maybe you have a bad sector of that drive and is hanging. Maybe some new settings for new update you need to do, be aware of this PSA from LND guys, valid for core 28.0.1 with LND. https://xcancel.com/roasbeef/status/1842956355516223824

0 sats \ 6 replies \ @siggy47 OP 8 Jan

I guess it's possible that I didn't wait long enough, but it took a while to say "running", then it switched to "starting" about an hour later.

41 sats \ 5 replies \ @DarthCoin 8 Jan

logs. You need logs, otherwise we are just guessing around.

110 sats \ 4 replies \ @siggy47 OP 8 Jan

This is exactly what I am dealing with: https://community.start9.com/t/bitcoin-core-continually-status-starting/1852

41 sats \ 2 replies \ @nym 8 Jan

Your SIGBUS error could be due to not enough swap space. You could use htop to check.

What is your bitcoin.conf and electrs.conf configuration, minus RPC info.

You can manually check the RPC connection like this if you're using RPC username and password:

bitcoin-cli -rpcuser=your_rpc_username -rpcpassword=your_rpc_password getblockchaininfo

0 sats \ 0 replies \ @siggy47 OP 8 Jan

I'm not a real technical guy. I do know I had ZeroMQ enables, and a transaction index. I don't know if that helps.

0 sats \ 0 replies \ @siggy47 OP 8 Jan

I need to install core first, but I think I can tell you if you have specific questions, since I set it up how embassy recommended

41 sats \ 0 replies \ @DarthCoin 8 Jan

Replace the RAM with ECC ones (if the motherboard will support it). Or first, just try to take them out clean them with some alcohol and put them back, sometimes the contacts are getting rusted.

But anyways, for a full node I will recommend ECC RAM, especially for a LN node.

Another cause for SIGBUS error is the power supply. Cannot give the right voltage to the RAM and this is failing. If you can get an extra power source to test will be great.

SIGBUS comes from "segmentation bus". Is something wrong on your memory bus.

So yeah I will start in small steps:

clean the RAM contacts... try again. If it fails, go to step 2
change the power source. if it fails, go to step 3
change the RAM, with ECC