Electrum server discussion thread

[unclemantis]

Until the servers can be more stable and the windows version of the application can connect to the servers on a constant basis, I will be using Multibit which I am happy to say is more forgiving of glitches. There is even a nifty rollback feature.

[1714019128]

1714019128

[1714019128]

1714019128

[1714019128]

1714019128

[1714019128]

1714019128

[1714019128]

1714019128

[Tachikoma]

Until the servers can be more stable and the windows version of the application can connect to the servers on a constant basis, I will be using Multibit which I am happy to say is more forgiving of glitches. There is even a nifty rollback feature.

This feels kinda passive aggressive in my humble opinion. You post in a thread to tell us you are _not_ using the client the thread is dedicated to.

[unclemantis]

Until the servers can be more stable and the windows version of the application can connect to the servers on a constant basis, I will be using Multibit which I am happy to say is more forgiving of glitches. There is even a nifty rollback feature.

This feels kinda passive aggressive in my humble opinion. You post in a thread to tell us you are _not_ using the client the thread is dedicated to.

You make me sound like a Troll

[JompinDox]

I'm thinking of setting up a server... Just wondering, how many users connect to a given server per day, on average?

[Tuxavant]

Where can I get the latest stratum software?

[flatfly]

Where can I get the latest stratum software?

Should be here:
 https://github.com/spesmilo/electrum-server

[Tuxavant]

Thanks Flatfly.... Throwing some errors when applying the patches..

Code:

$ patch -p 2 < ~/src/electrum/server/patches/bitcoin-0.6.2.diff 
patching file bitcoinrpc.cpp
Hunk #1 FAILED at 1497.
Hunk #2 FAILED at 1933.
Hunk #3 FAILED at 2055.
3 out of 3 hunks FAILED -- saving rejects to file bitcoinrpc.cpp.rej
patching file main.cpp
Hunk #1 FAILED at 3134.
1 out of 1 hunk FAILED -- saving rejects to file main.cpp.rej
patching file main.h
Hunk #1 FAILED at 395.
Hunk #2 FAILED at 416.
2 out of 2 hunks FAILED -- saving rejects to file main.h.rej

[bitfoo]

Thanks Flatfly.... Throwing some errors when applying the patches..

Code:

$ patch -p 2 < ~/src/electrum/server/patches/bitcoin-0.6.2.diff 

The latest bitcoin patch I see on git is bitcoin-0.6.3 diff. Are you trying to apply bitcoin-0.6.2.diff to bitcoin 0.6.3?

[Tuxavant]

good call... it was indeed the wrong patch/version, but then,

There doesn't appear to be a ..../bitcoin-0.6.3.diff patch file, so I went with 0.6.2

Code:

$ tar zxvf bitcoin-0.6.2.tgz 
bitcoin@host:~/src$ mv bitcoin-bitcoin-06d764e bitcoin-0.6.2
bitcoin@host:~/src$ cd bitcoin-0.6.2
bitcoin@host:~/src/bitcoin-0.6.2$ patch -p 2 < ~/src/electrum/server/patches/bitcoin-0.6.2.diff 
patching file bitcoinrpc.cpp
Hunk #1 FAILED at 1497.
Hunk #2 FAILED at 1933.
Hunk #3 FAILED at 2055.
3 out of 3 hunks FAILED -- saving rejects to file bitcoinrpc.cpp.rej
patching file main.cpp
Hunk #1 FAILED at 3134.
1 out of 1 hunk FAILED -- saving rejects to file main.cpp.rej
patching file main.h
Hunk #1 FAILED at 395.
Hunk #2 FAILED at 416.
2 out of 2 hunks FAILED -- saving rejects to file main.h.rej

[ErebusBat]

There doesn't appear to be a ..../bitcoin-0.6.3.diff patch file

Are you sure you are on the correct version/branch in git?  Can you post your commit hash?

[Tuxavant]

Are you sure you are on the correct version/branch in git?  Can you post your commit hash?

Code:

$ git show
commit d659a2f2020b052c8c33f4903091f2d0e64398f2

[Tachikoma]

Are you sure you are on the correct version/branch in git?  Can you post your commit hash?

Code:

$ git show
commit d659a2f2020b052c8c33f4903091f2d0e64398f2

I think you are on the wrong branch or repo. Here is a direct link to the 6.3 patch.

[slush]

Independent server monitoring: https://bitcointalk.org/index.php?topic=112413.0

[Tachikoma]

Independent server monitoring: https://bitcointalk.org/index.php?topic=112413.0

First implementation online, see this post.

[duncant]

Hi all!

I've been trying to move my server uncle-enzo.info to a new/better host uncle-enzo.mit.edu, but things have gone horribly wrong.

The initial abe import went just fine. I can start the server and it prints the correct number of blocks. When I fire up my client, the server prints a flurry of "discarding tx id ..." messages followed by the typical "[<datetime>] TCP <ip address> <bitocin address> <address count> <client version>" message. After that, everything just hangs. My client gets stuck on "Connecting..." and nothing more interesting happens on the server end.

Do you have any idea what could be going on? Thank you!

[Tachikoma]

Can you reach Bitcoind normally? bitcoind getbalance etc. works?

[duncant]

Yes. Bitcoind responds to all its commands appropriately.

[duncant]

During startup, the server prints the following error message. Perhaps this has something to do with the problem I'm having?

Code:

Exception in thread Thread-2:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 551, in __bootstrap_inner
    self.run()
  File "/usr/share/electrum-server/processor.py", line 246, in run
    self.update()
  File "/usr/share/electrum-server/processor.py", line 260, in update
    self.send_response(internal_id, response)
  File "/usr/share/electrum-server/processor.py", line 276, in send_response
    session.send_response(response)
  File "/usr/share/electrum-server/transports/stratum_tcp.py", line 30, in send_response
    data = json.dumps(response) + "\n"
  File "/usr/lib/python2.7/json/__init__.py", line 231, in dumps
    return _default_encoder.encode(obj)
  File "/usr/lib/python2.7/json/encoder.py", line 201, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib/python2.7/json/encoder.py", line 264, in iterencode
    return _iterencode(o, 0)
  File "/usr/lib/python2.7/json/encoder.py", line 178, in default
    raise TypeError(repr(o) + " is not JSON serializable")
TypeError: <read-only buffer for 0x48db490, size 25, offset 0 at 0x48fc870> is not JSON serializable

[ThomasV]

Hi all!

I've been trying to move my server uncle-enzo.info to a new/better host uncle-enzo.mit.edu, but things have gone horribly wrong.

The initial abe import went just fine. I can start the server and it prints the correct number of blocks. When I fire up my client, the server prints a flurry of "discarding tx id ..." messages followed by the typical "[<datetime>] TCP <ip address> <bitocin address> <address count> <client version>" message. After that, everything just hangs. My client gets stuck on "Connecting..." and nothing more interesting happens on the server end.

Do you have any idea what could be going on? Thank you!

I would try to rebuild of the abe database from scratch. (I know, it is slow...)

[ErebusBat]

I would try to rebuild of the abe database from scratch. (I know, it is slow...)

See ya in 3 weeks duncant :/