The September Bitcoin test/demonstration/spam attack/DDoS attack has begun. Now is the time for all Electrum Server operators to check how their node is standing up, including looking at the processor loading used by Electrum and Bitcoind.
Topic: Electrum server discussion thread - page 6. (Read 61487 times)
First time I built the db I thought it was hung a couple of time, too. But it really wasn't, just taking very long.
I ended up using a db download.
I ended up using a db download.
I built a DB (1000 limit) from scratch back in April - it took 5 weeks
Much better to DL one
Everytime I download it fails the md5 check.
The first 170K is fine - the next 200K will take forever
yes.. i noticed by myself.
even on a 30 GB Ramdisk and fast CPU..
What is the main point which takes that long?
Request from bitcoind? generate the DB?..
Hi,
I have just finished Electrum LTC server up and running, but I have" small" issue left.
All working fine when I connected to Electrum client from localhost.
But I like to get work also as public server.
The problem is that, TCP and SSL sockets could not open...I don't know why.
[05/08/2015-15:36:26] Blockchain height 828417
[05/08/2015-15:36:26] UTXO tree root hash: dd4cdb5b61e1d92b50b745b3d758b62c98bb2fc9b28925033cb6c8c0667aa8ca
[05/08/2015-15:36:26] Coins in database: 4141945190326061
[05/08/2015-15:36:26] could not open TCP socket on zz.xx.cc.vv:50001
[05/08/2015-15:36:26] could not open SSL socket on zz.xx.cc.vv.:50002
[05/08/2015-15:36:26] Blockchain is up to date.
[05/08/2015-15:36:26] Memory pool initialized.
[05/08/2015-15:36:26] blockchain: 828418 (0.005s)
[05/08/2015-15:36:26] litecoind is responding
[05/08/2015-15:36:27] joining IRC
IRC connect is OK.
"electrum-ltc-server peers" -command prints my nick name correctly.
Port forwarding has done to these two ports (50001 and 50002) and iptables should be ok. Also ports 50001 and 50002 are open.
Could someone help me with this issue?
Thank you!
I have just finished Electrum LTC server up and running, but I have" small" issue left.
All working fine when I connected to Electrum client from localhost.
But I like to get work also as public server.
The problem is that, TCP and SSL sockets could not open...I don't know why.
[05/08/2015-15:36:26] Blockchain height 828417
[05/08/2015-15:36:26] UTXO tree root hash: dd4cdb5b61e1d92b50b745b3d758b62c98bb2fc9b28925033cb6c8c0667aa8ca
[05/08/2015-15:36:26] Coins in database: 4141945190326061
[05/08/2015-15:36:26] could not open TCP socket on zz.xx.cc.vv:50001
[05/08/2015-15:36:26] could not open SSL socket on zz.xx.cc.vv.:50002
[05/08/2015-15:36:26] Blockchain is up to date.
[05/08/2015-15:36:26] Memory pool initialized.
[05/08/2015-15:36:26] blockchain: 828418 (0.005s)
[05/08/2015-15:36:26] litecoind is responding
[05/08/2015-15:36:27] joining IRC
IRC connect is OK.
"electrum-ltc-server peers" -command prints my nick name correctly.
Port forwarding has done to these two ports (50001 and 50002) and iptables should be ok. Also ports 50001 and 50002 are open.
Could someone help me with this issue?
Thank you!
Problem solved.
Configuration problem on /etc/electrum-ltc.conf -file.
Should be:
"host = 192.168.1.33"
not FQDN address.
Also, there's no support whatsoever for Electrum and altcoins here...
Hi,
I have just finished Electrum LTC server up and running, but I have" small" issue left.
All working fine when I connected to Electrum client from localhost.
But I like to get work also as public server.
The problem is that, TCP and SSL sockets could not open...I don't know why.
[05/08/2015-15:36:26] Blockchain height 828417
[05/08/2015-15:36:26] UTXO tree root hash: dd4cdb5b61e1d92b50b745b3d758b62c98bb2fc9b28925033cb6c8c0667aa8ca
[05/08/2015-15:36:26] Coins in database: 4141945190326061
[05/08/2015-15:36:26] could not open TCP socket on zz.xx.cc.vv:50001
[05/08/2015-15:36:26] could not open SSL socket on zz.xx.cc.vv.:50002
[05/08/2015-15:36:26] Blockchain is up to date.
[05/08/2015-15:36:26] Memory pool initialized.
[05/08/2015-15:36:26] blockchain: 828418 (0.005s)
[05/08/2015-15:36:26] litecoind is responding
[05/08/2015-15:36:27] joining IRC
IRC connect is OK.
"electrum-ltc-server peers" -command prints my nick name correctly.
Port forwarding has done to these two ports (50001 and 50002) and iptables should be ok. Also ports 50001 and 50002 are open.
Could someone help me with this issue?
Thank you!
I have just finished Electrum LTC server up and running, but I have" small" issue left.
All working fine when I connected to Electrum client from localhost.
But I like to get work also as public server.
The problem is that, TCP and SSL sockets could not open...I don't know why.
[05/08/2015-15:36:26] Blockchain height 828417
[05/08/2015-15:36:26] UTXO tree root hash: dd4cdb5b61e1d92b50b745b3d758b62c98bb2fc9b28925033cb6c8c0667aa8ca
[05/08/2015-15:36:26] Coins in database: 4141945190326061
[05/08/2015-15:36:26] could not open TCP socket on zz.xx.cc.vv:50001
[05/08/2015-15:36:26] could not open SSL socket on zz.xx.cc.vv.:50002
[05/08/2015-15:36:26] Blockchain is up to date.
[05/08/2015-15:36:26] Memory pool initialized.
[05/08/2015-15:36:26] blockchain: 828418 (0.005s)
[05/08/2015-15:36:26] litecoind is responding
[05/08/2015-15:36:27] joining IRC
IRC connect is OK.
"electrum-ltc-server peers" -command prints my nick name correctly.
Port forwarding has done to these two ports (50001 and 50002) and iptables should be ok. Also ports 50001 and 50002 are open.
Could someone help me with this issue?
Thank you!
Problem solved.
Configuration problem on /etc/electrum-ltc.conf -file.
Should be:
"host = 192.168.1.33"
not FQDN address.
Hi,
I have just finished Electrum LTC server up and running, but I have" small" issue left.
All working fine when I connected to Electrum client from localhost.
But I like to get work also as public server.
The problem is that, TCP and SSL sockets could not open...I don't know why.
[05/08/2015-15:36:26] Blockchain height 828417
[05/08/2015-15:36:26] UTXO tree root hash: dd4cdb5b61e1d92b50b745b3d758b62c98bb2fc9b28925033cb6c8c0667aa8ca
[05/08/2015-15:36:26] Coins in database: 4141945190326061
[05/08/2015-15:36:26] could not open TCP socket on zz.xx.cc.vv:50001
[05/08/2015-15:36:26] could not open SSL socket on zz.xx.cc.vv.:50002
[05/08/2015-15:36:26] Blockchain is up to date.
[05/08/2015-15:36:26] Memory pool initialized.
[05/08/2015-15:36:26] blockchain: 828418 (0.005s)
[05/08/2015-15:36:26] litecoind is responding
[05/08/2015-15:36:27] joining IRC
IRC connect is OK.
"electrum-ltc-server peers" -command prints my nick name correctly.
Port forwarding has done to these two ports (50001 and 50002) and iptables should be ok. Also ports 50001 and 50002 are open.
Could someone help me with this issue?
Thank you!
I have just finished Electrum LTC server up and running, but I have" small" issue left.
All working fine when I connected to Electrum client from localhost.
But I like to get work also as public server.
The problem is that, TCP and SSL sockets could not open...I don't know why.
[05/08/2015-15:36:26] Blockchain height 828417
[05/08/2015-15:36:26] UTXO tree root hash: dd4cdb5b61e1d92b50b745b3d758b62c98bb2fc9b28925033cb6c8c0667aa8ca
[05/08/2015-15:36:26] Coins in database: 4141945190326061
[05/08/2015-15:36:26] could not open TCP socket on zz.xx.cc.vv:50001
[05/08/2015-15:36:26] could not open SSL socket on zz.xx.cc.vv.:50002
[05/08/2015-15:36:26] Blockchain is up to date.
[05/08/2015-15:36:26] Memory pool initialized.
[05/08/2015-15:36:26] blockchain: 828418 (0.005s)
[05/08/2015-15:36:26] litecoind is responding
[05/08/2015-15:36:27] joining IRC
IRC connect is OK.
"electrum-ltc-server peers" -command prints my nick name correctly.
Port forwarding has done to these two ports (50001 and 50002) and iptables should be ok. Also ports 50001 and 50002 are open.
Could someone help me with this issue?
Thank you!
First time I built the db I thought it was hung a couple of time, too. But it really wasn't, just taking very long.
I ended up using a db download.
I ended up using a db download.
I built a DB (1000 limit) from scratch back in April - it took 5 weeks
Much better to DL one
Everytime I download it fails the md5 check.
The first 170K is fine - the next 200K will take forever
First time I built the db I thought it was hung a couple of time, too. But it really wasn't, just taking very long.
I ended up using a db download.
I ended up using a db download.
I built a DB (1000 limit) from scratch back in April - it took 5 weeks
Much better to DL one
Everytime I download it fails the md5 check.
First time I built the db I thought it was hung a couple of time, too. But it really wasn't, just taking very long.
I ended up using a db download.
I ended up using a db download.
I built a DB (1000 limit) from scratch back in April - it took 5 weeks
Much better to DL one
So now I'm in the process of rebuilding the server's db because apparently mine was incorrect, it was giving the wrong hash.
But the server hangs during block import every few blocks and I have to kill and restart it.
But the server hangs during block import every few blocks and I have to kill and restart it.
Are you sure it hangs? Can you look at cpu and io load during the "hang"?
First time I built the db I thought it was hung a couple of time, too. But it really wasn't, just taking very long.
I ended up using a db download.
So now I'm in the process of rebuilding the server's db because apparently mine was incorrect, it was giving the wrong hash.
But the server hangs during block import every few blocks and I have to kill and restart it.
But the server hangs during block import every few blocks and I have to kill and restart it.
I believe I am correctly running a public Electrum node at btc.mustyoshi.com:50001
You server doesn't seem to be connected on IRC... So no, you're not correctly running a public Electrum node
EDIT: So apparently report_host can't be the same as host.
host is the IP of the server
report_host is the FQDN of the server
I believe I am correctly running a public Electrum node at btc.mustyoshi.com:50001
You server doesn't seem to be connected on IRC... So no, you're not correctly running a public Electrum node
EDIT: So apparently report_host can't be the same as host.
I believe I am correctly running a public Electrum node at btc.mustyoshi.com:50001
You server doesn't seem to be connected on IRC... So no, you're not correctly running a public Electrum node
I believe I am correctly running a public Electrum node at btc.mustyoshi.com:50001
It looks like the leveldb dumps are not updated in the foundry:
http://foundry.electrum.org/leveldb-dump/?C=M;O=D
Last dump is from July 8.
http://foundry.electrum.org/leveldb-dump/?C=M;O=D
Last dump is from July 8.
It used to be daily...
I update the 1000 limit weekly (on Saturday).
Mostly it is done once a week
It looks like the leveldb dumps are not updated in the foundry:
http://foundry.electrum.org/leveldb-dump/?C=M;O=D
Last dump is from July 8.
http://foundry.electrum.org/leveldb-dump/?C=M;O=D
Last dump is from July 8.
I believe there is a 48hours timeout...so if you haven't confirmed them yet, they should come back into your wallet.
Thanks. I'm not worried. One way or another, I'll get the bitcoins back since I sent them from my bitcoin core wallet to my Electrum wallet. And they were pocket change, compared to the amount I've previously lost thanks to scamming bitcoin miner companies...
I believe there is a 48hours timeout...so if you haven't confirmed them yet, they should come back into your wallet.
Electrum-server used 5832 seconds to process one block! This is a bug. Not a slow processor.
I wouldn't say that it is a bug, but instead, not optimized for slow processors, or bloated blocks, full of useless UTXOs that the Bitcoin spammer is currently injecting in the network today...
... over 50k transactions are in the waiting room at the moment, waiting to be included into a block... https://chain.so/BTC
If senders didn't put at least 0.0005 BTC per kb, as transaction fees, the waiting time to be included into a block is... 16h
One of those transactions is mine. I sent it from my Bitcoin Core 10.2 wallet with the default transaction cost. I believe this was a bug, with less than 1000 Satoshi's as fee. It has been sitting unconfirmed for 24 hours. I am sure that lots of other people are in the same boat. About the only way to put it is, "Bitcoin is experimental. It is not ready for production use by normal people." These problems will either be fixed or bitcoin will cease to exist.
Jump to: