Thanks for the answers ThomasV and Marcus.
I think Slush posted a torrent somewhere, I hope this might speed up the initial blockchain import, not sure how old that is by now. To be sure I will assign it 2GB and see how it behaves.
I think ecdsa.org might have crashed again btw, I have pending transaction that is confirmed on the other servers.
Topic: Electrum server discussion thread - page 21. (Read 61494 times)
Can I ask you what kind of resources a electrum server uses or rather what kind of resources I should dedicate to it to have it running stable.
The HOWTO is instructive http://gitorious.org/electrum/server/blobs/master/HOWTO
I thought this was a consideration ....
Quote
Important notice: This is a *very* long process. Even on fast machines you can expect it to take hours. Here are some benchmarks for importing ~173.000 blocks (size of the Bitcoin blockchain at the time of this writing):
System 1: ~9 hours.
* CPU: Intel Core i7 Q740 @ 1.73GHz
* HDD: very fast SSD
System 2: ~55 hours.
* CPU: Intel Xeon X3430 @ 2.40GHz
* HDD: 2 x SATA in a RAID1.
System 1: ~9 hours.
* CPU: Intel Core i7 Q740 @ 1.73GHz
* HDD: very fast SSD
System 2: ~55 hours.
* CPU: Intel Xeon X3430 @ 2.40GHz
* HDD: 2 x SATA in a RAID1.
Can I ask you what kind of resources a electrum server uses or rather what kind of resources I should dedicate to it to have it running stable.
my server (ecdsa.org) runs on a vps hosted by cinfu.com, with 1GB of RAM
I had crashes in the last few days because I was working on the server code;
the traffic increase caused by SatoshiDice forced me to make my bitcoind patch more efficient..
I believe this is fixed. bitcoind has been running for 24h and does not crash anymore.
However, its memory usage slowly increases; there might be a memory leak.
The total memory usage right now is 630M. This is bitcoind + the electrum server in python.
(note that the electrum server never removes elements from its cache, so in principle this is another leak that should be fixed.
in practice, however, bitcoind eats much more)
Can I ask you what kind of resources a electrum server uses or rather what kind of resources I should dedicate to it to have it running stable.
here is another update to the patch.
the pevious version did not return orphaned transactions in getmemorypool
https://gitorious.org/electrum/server/commit/a1156626e746cd847bb0a02344bfb57993fd1c80
the pevious version did not return orphaned transactions in getmemorypool
https://gitorious.org/electrum/server/commit/a1156626e746cd847bb0a02344bfb57993fd1c80
I just pushed another important update with a new bitcoind patch.
it fixes memorypool issues.
it fixes memorypool issues.
This is more a question about the design philosophy of the server than specifics;
Why SQL database?
because I use abe.
This is more a question about the design philosophy of the server than specifics;
Why SQL database?
I just added a very basic DOS protection to the server code:
addresses with more than 200 inputs or output transactions will raise an error.
this means protection agains requests of the history of popular addresses (eg Satoshi Dice)
addresses with more than 200 inputs or output transactions will raise an error.
this means protection agains requests of the history of popular addresses (eg Satoshi Dice)
will you loose any coins?
can you explain your question?
The new version of what? the client or the server?
This thread is about the server, and the server does not manage your coins; the client does.
This is why your question did not make sense to me.
Please clarify. do you run an Electrum server?
will you loose any coins?
can you explain your question?
will you loose any coins?
can you explain your question?
will you loose any coins?
can you explain your question?
will you loose any coins?
can you explain your question?
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? 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.
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.
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.
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
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
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?
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.
Jump to: