-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't establish connection to backend: dial tcp: missing address #43
Comments
Defined redis section in unlocker conf, now it finally started. Another question - all blocks have been counted as new so far, no any immature. So it does not unlock any again. Some of them are few days old. Please suggest what special must be done to make the pool change the state of "new" blocks. |
Sync chain. Run unlocker. |
root@ip#:~/open-ethereum-pool# ./ether-pool ./unlocker.json loop. How many blocks to wait? |
In issue #24 HelixR wrote he run it with config where were unlocker and payout only and that worked out. Will that be ok as you strongly recommend to run unlocker and only then payout? |
Yes I strongly recommend, but this is not an issue. |
Depends on depth serttings. |
immatureDepth is 20 (default) and depth is 120 (also default). I believe the last is okay as there's already 2184 block mined back. root@ip:~/open-ethereum-pool# ./ether-pool ./unlocker.json still :( |
Create a gist with a config file, remove sensitive data and show me, |
make sure you have this param in unlocker config https://github.com/sammy007/open-ethereum-pool/blob/master/config.example.json#L3 |
https://gist.github.com/eug13768 Although I did not try to run payouts unless unlocker fnished okay. Oh, yeah! Your last advice about adding "coin" did help! 2016/07/25 18:46:45 Mature block 1934666 with 1 tx, hash: 0x101d60ef |
Please wait a second, let me run payouts. |
I see your blocks are now immature, let them mature now. |
For payouts make sure your coinbase account is unlocked with Account must be permanently unlocked. |
Now it shows Blocks: 2184 Immature: 0 New; 2 Yes, geth is running with --unlock. Anything special to add to payouts.json ("coin": "eth")? |
Usually configs must be equal just enabled/disable particular modules. |
Payouts go. Thank you for your help! |
Good luck with your classic pool, make sure |
It's there and will stay there - you should have some ETC when the process finish and further. |
I suggest you to rise payout threshold to 1 Ether otherwise your payouts will last forever. |
System information
Geth version:
geth version
or commit hash ifdevelop
Version: 1.4.9-stable-b7e3dfc5
Protocol Versions: [63 62 61]
Network Id: 1
Go Version: go1.6.2
OS: linux
GOPATH=/home/ubuntu/go
GOROOT=/opt/google/go
Redis version:
redis-server --version
Redis server v=2.8.4 sha=00000000:0 malloc=jemalloc-3.4.1 bits=64 build=a44a05d76f06a5d9
OS & Version: Linux/Ubuntu 14.04
Commit branch and hash: (
master
,ba60e1c
)Expected behaviour
Unlocker does its job
Actual behaviour
2016/07/25 12:59:36 Loading config: /home/ubuntu/open-ethereum-pool/unlocker.json
2016/07/25 12:59:36 Can't establish connection to backend: dial tcp: missing address
2016/07/25 12:59:36 Starting block unlocker
2016/07/25 12:59:36 Set block unlock interval to 10m0s
2016/07/25 12:59:36 Failed to get block candidates from backend: dial tcp: missing address
2016/07/25 12:59:36 Unlocking suspended due to last critical error: dial tcp: missing address
This error appears when running separate instance of ether-pool with unlocker.json:
{
"unlocker": {
"enabled": true,
"poolFee": 0.9,
"poolFeeAddress": "0x<some_address_set_here>",
"donate": true,
"depth": 120,
"immatureDepth": 20,
"interval": "10m",
"daemon": "http://127.0.0.1:8545",
"keepTxFees": false,
"timeout": "10s"
}
}
Please suggest what can be the issue.
The text was updated successfully, but these errors were encountered: