-
Notifications
You must be signed in to change notification settings - Fork 343
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
Server crash soon after start on 'ill-formed response error object: no new valid entries' #27
Comments
duplicate of #22 |
I think this issue was closed in prematurely... I'm seeing this same crash repeatedly on my linux box (fedora 32) using the latest git 1.15 label, but there aren't two instances. Just the one. I have to re-start the server 3-4 times before it runs for a decent amount of time, but usually after a few hours, the same crash happens again. Same python traceback error as above. |
I think the fix is not in 1.15. You have to use master or wait for the next release. It fixed the issue for me. |
Ahh OK cool, I'll give master a whirl. Thanks! |
Ugh. Tried master but it didn't like my config file (COIN=BitcoinSegwit). Tried to set COIN=Bitcoin, but it still complained that Bitcoin+mainnet is a bad combo (I don't have a NET specified right now). What should I be using for BTC? |
That should work fine. Can you post your config? I have
|
Update: I think this was pilot error, I was using the old kyuupichan repo by mistake. Looks like it's starting OK right now. Lightly scrubbed for security reasons: http://prowlers.com/~cdavis/electrumx.conf |
That is weird. Could you also post the logs for the startup sequence? Could it be possible that your config is not being used? |
It was my mistake. I stupidly built from the kyuupichan repo (old habits die hard) this morning. My server seems to be running normally again. Thanks again for your help. |
Version 1.15.0, Ubuntu focal
Server starts up, but soon after crashes. On first look it seems like a problem with some peer. I'll investigate further. Here are the logs:
The text was updated successfully, but these errors were encountered: