Electrum server discussion thread - page 22.

Tuxavant

hero member

Activity: 784

Merit: 1010

Bitcoin Mayor of Las Vegas

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

legendary

Activity: 1896

Merit: 1353

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

ThomasV

legendary

Activity: 1896

Merit: 1353

Quote from: anfedorov on June 10, 2012, 08:15:48 PM

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

legendary

Activity: 1896

Merit: 1353

Quote from: anfedorov on June 10, 2012, 08:15:48 PM

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.

Tuxavant

hero member

Activity: 784

Merit: 1010

Bitcoin Mayor of Las Vegas

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.

NothinG

hero member

Activity: 560

Merit: 500

Quote from: TheBitMan on June 10, 2012, 10:22:06 PM

everything is down..no server connection

I've got connection to uncle-enzo.info

TheBitMan

sr. member

Activity: 280

Merit: 250

everything is down..no server connection

anfedorov

newbie

Activity: 44

Merit: 0

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?

ThomasV

legendary

Activity: 1896

Merit: 1353

Quote from: duncant on June 09, 2012, 10:26:02 PM

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.

duncant

jr. member

Activity: 53

Merit: 2

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.

marcus_of_augustus

legendary

Activity: 3920

Merit: 2349

Eadem mutata resurgo

watching.

ThomasV

legendary

Activity: 1896

Merit: 1353

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.

Topic: Electrum server discussion thread - page 22. (Read 61509 times)