-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting receiving on an empty and disconnected channel running in docker #1055
Comments
Looks like your bitcoind got shutdown, can you check its logs? |
No, Its running - http://68.183.80.225:38332 wondering what could've gone wrong |
Please check the logs from around 17:08:04, bitcoind should say some reason why it disconnects. |
I guess you need to increase verbosity of bitcoind somehow. |
Is it possible that you're missing |
but it takes default value for |
Yes but you've set signet challenge which might affect it but I don't really have much knowledge here. Just guessing. |
Ok, do you think may be due to this error ? Error: Cannot obtain a lock on data directory /root/.bitcoin/signet. Bitcoin Core is probably already running. i can see this error on startup.. do you know how to clear that ? |
bitcoin core probably disconnects electrs because the network magic is wrong, see https://en.bitcoin.it/wiki/Signet "The protocol message header bytes are dynamically generated based on the block challenge" ('message header bytes' is the exact same thing as 'network magic') |
Thanks a lot for your response, do you know how to calculate and set network magic in bitcoin conf ? |
You need to set it in electrs, not bitcoin.conf. I don't know how to calculate it. |
its available in the signet debug logs as well, Got it thanks for the help |
The same Bitcoin wiki page also mentions how to calculate the megic bytes from the signet challenge, the first 4 bytes of https://en.bitcoin.it/wiki/Signet#Genesis_Block_and_Message_Header |
I have the exact same problem on mainnet for some days `Electrum attempting reconnect... Caused by: Caused by: |
Getting following error in the electrs, can you please help me what might be the wrong
electrs error log,
bitcoin.conf file
The text was updated successfully, but these errors were encountered: