Electrum server discussion thread

[ThomasV]

This thread is for announcements and questions concerning the Electrum server code.
You want to subscribe to it if you run an Electrum server.

________________________________


Today we just fixed a bug in bitcoin-abe, that was causing a memory allocation error.
https://github.com/jtobey/bitcoin-abe/commit/0b7f464b52454555c69a6b77b4ad0cf453a2cf48

The bug was silent because exceptions thrown by the library were not properly logged.
This is fixed too; exceptions thrown by the library are logged, and the server will enter its 'server not ready' status when such an exception is raised.

If you are a server operator, please pull the latest version of both abe and of the Electrum server.
Do not forget to reinstall the abe library ('python setup.py install') prior to restarting the electrum server.

[1714478538]

1714478538

[1714478538]

1714478538

[1714478538]

1714478538

[marcus_of_augustus]

watching.

[duncant]

I've been having some trouble with my server, uncle-enzo.info , getting killed by (what I assume is) an out of memory problem. I didn't have this problem before I upgraded to the lastest version of abe and electrum-server.

I'm going to try to debug it further and get back to you.

[ThomasV]

I've been having some trouble with my server, uncle-enzo.info , getting killed by (what I assume is) an out of memory problem. I didn't have this problem before I upgraded to the lastest version of abe and electrum-server.

I'm going to try to debug it further and get back to you.

I have always had memory problems with the server.
the memory used by bitcoind increases slowly but regularly; my patches may have introcuced a memory leak, but I did not find it.
electrum_server reads the memory pool every 10 seconds. this is pretty intensive, and could also cause this leak.

[anfedorov]

For the last couple of hours, the servers at ecdsa.org, btcback.com, and electrum.novit.ro have been responding to:

--> {"params": [], "id": 2, "method": "blockchain.numblocks.subscribe"}

with:

<-- {"id": 2, "result": 0}

Which seems... unlikely. Any idea of what could be causing it?

[TheBitMan]

everything is down..no server connection

[NothinG]

everything is down..no server connection

I've got connection to uncle-enzo.info

[Tuxavant]

Server connection is there (see debug info) but the client is erroneously reporting "no server connection" in place of a balance. If you run from the command line "electrum balance" you'll see the wallet balance.

[ThomasV]

For the last couple of hours, the servers at ecdsa.org, btcback.com, and electrum.novit.ro have been responding to:

--> {"params": [], "id": 2, "method": "blockchain.numblocks.subscribe"}

with:

<-- {"id": 2, "result": 0}

Which seems... unlikely. Any idea of what could be causing it?

bitcoind crashed at ecdsa.org.

[ThomasV]

For the last couple of hours, the servers at ecdsa.org, btcback.com, and electrum.novit.ro have been responding to:

--> {"params": [], "id": 2, "method": "blockchain.numblocks.subscribe"}

with:

<-- {"id": 2, "result": 0}

Which seems... unlikely. Any idea of what could be causing it?

this is the answer returned by the server when the local bitcoin daemon cannot be reached.
this causes the client to display "server not ready"

[ThomasV]

we are having problems with ecdsa.org and electrum.novit.ro
both servers are down.
sorry for the inconvenience.

[Tuxavant]

Dunno if this will be helpful, but this is how I keep bitcoind running on my tor exit servers:

Code:

2012-06-11:0803 EDT
[redacted@tor-exit-alpha ~]$ crontab -l
*/5 * * * * /home/redacted/bin/check-bitcoind &> /dev/null


2012-06-11:0803 EDT
[redacted@tor-exit-alpha ~]$ cat /home/redacted/bin/check-bitcoind 
#!/bin/bash

pgrep "^bitcoind$" &> /dev/null
if [ $? -gt 0 ]; then
  echo "bitcoind not running. Starting process..."
  /usr/local/bin/bitcoind &
else
  echo "bitcoind is alive."
  true
fi

[ThomasV]

Dunno if this will be helpful, but this is how I keep bitcoind running on my tor exit servers:

bitcoind is fine. we just both upgraded Abe and it somehow corrupted our databases.
my server is back now.
I applied a workaround, but I still have to understand what really happened, and if the database is ok.

[duncant]

I see that bitcoin-abe and electrum/server have been updated. Should I go ahead an upgrade or should I wait until everything is stable?

[duncant]

I see that bitcoin-abe and electrum/server have been updated. Should I go ahead an upgrade or should I wait until everything is stable?

Well, I went ahead and upgraded (after making a backup of the database). The server is outputting messages like those below. Should I be worried/should I restore from backup and downgrade?

Code:

block number: 184242
WARNING: missing tx_in for tx 3977349
WARNING: missing tx_out for tx 3977349
block number: 184243
WARNING: missing tx_in for tx 3977352
block number: 184244
WARNING: missing tx_in for tx 3977356
block number: 184245
WARNING: missing tx_in for tx 3977404
block number: 184246
WARNING: missing tx_in for tx 3977413
block number: 184247
WARNING: missing tx_in for tx 3977461
block number: 184248

[ThomasV]

I see that bitcoin-abe and electrum/server have been updated. Should I go ahead an upgrade or should I wait until everything is stable?

Well, I went ahead and upgraded (after making a backup of the database). The server is outputting messages like those below. Should I be worried/should I restore from backup and downgrade?

Code:

block number: 184242
WARNING: missing tx_in for tx 3977349
WARNING: missing tx_out for tx 3977349
block number: 184243
WARNING: missing tx_in for tx 3977352
block number: 184244
WARNING: missing tx_in for tx 3977356
block number: 184245
WARNING: missing tx_in for tx 3977404
block number: 184246
WARNING: missing tx_in for tx 3977413
block number: 184247
WARNING: missing tx_in for tx 3977461
block number: 184248

no, don't worry. I added these warnings after the last schema change in abe, but they seem to be harmless.

[ThomasV]

today I fixed a major performance issue with the server.

if you upgrade, please note that I updated the bitcoind patch. (for 0.6.2)
you need to recompile bitcoind with this new patch in order to complete the upgrade.

[TheBitMan]

today I fixed a major performance issue with the server.

if you upgrade, please note that I updated the bitcoind patch. (for 0.6.2)
you need to recompile bitcoind with this new patch in order to complete the upgrade.

will you loose any coins?

[ThomasV]

will you loose any coins?

can you explain your question?

[TheBitMan]

will you loose any coins?

can you explain your question?

When I update it, will I still have my coins afterword?