Skip to content
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

Closed
eug13768 opened this issue Jul 25, 2016 · 19 comments
Closed

Can't establish connection to backend: dial tcp: missing address #43

eug13768 opened this issue Jul 25, 2016 · 19 comments

Comments

@eug13768
Copy link

eug13768 commented Jul 25, 2016

System information

Geth version: geth version or commit hash if develop
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.

@eug13768
Copy link
Author

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.

@sammy007
Copy link
Owner

Please suggest what special must be done to make the pool change the state of "new" blocks.

Sync chain. Run unlocker.

@eug13768
Copy link
Author

eug13768 commented Jul 25, 2016

root@ip#:~/open-ethereum-pool# ./ether-pool ./unlocker.json
2016/07/25 16:43:40 Loading config: /home/ubuntu/open-ethereum-pool/unlocker.json
2016/07/25 16:43:40 Backend check reply: PONG
2016/07/25 16:43:40 Starting block unlocker
2016/07/25 16:43:40 Set block unlock interval to 10m0s
2016/07/25 16:43:40 No block candidates to unlock
2016/07/25 16:43:40 No immature blocks to credit miners
2016/07/25 16:53:40 No block candidates to unlock
2016/07/25 16:53:40 No immature blocks to credit miners

loop.

How many blocks to wait?

@eug13768
Copy link
Author

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?

@sammy007
Copy link
Owner

Yes I strongly recommend, but this is not an issue.

@sammy007
Copy link
Owner

How many blocks to wait?

Depends on depth serttings. immatureDepth must be default and you usually will get immature blocks after 32 blocks mined back. The depth param must be something close to 256 and will completely unlock block and credit balance.

@eug13768
Copy link
Author

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
2016/07/25 16:43:40 Loading config: /home/ubuntu/open-ethereum-pool/unlocker.json
2016/07/25 16:43:40 Backend check reply: PONG
2016/07/25 16:43:40 Starting block unlocker
2016/07/25 16:43:40 Set block unlock interval to 10m0s
2016/07/25 16:43:40 No block candidates to unlock
2016/07/25 16:43:40 No immature blocks to credit miners
2016/07/25 16:53:40 No block candidates to unlock
2016/07/25 16:53:40 No immature blocks to credit miners
2016/07/25 17:03:40 No block candidates to unlock
2016/07/25 17:03:40 No immature blocks to credit miners
2016/07/25 17:13:40 No block candidates to unlock
2016/07/25 17:13:40 No immature blocks to credit miners
2016/07/25 17:23:40 No block candidates to unlock
2016/07/25 17:23:40 No immature blocks to credit miners
2016/07/25 17:33:40 No block candidates to unlock
2016/07/25 17:33:40 No immature blocks to credit miners
2016/07/25 17:43:40 No block candidates to unlock
2016/07/25 17:43:40 No immature blocks to credit miners
2016/07/25 17:53:40 No block candidates to unlock
2016/07/25 17:53:40 No immature blocks to credit miners
2016/07/25 18:03:40 No block candidates to unlock
2016/07/25 18:03:40 No immature blocks to credit miners
2016/07/25 18:13:40 No block candidates to unlock
2016/07/25 18:13:40 No immature blocks to credit miners

still :(

@sammy007
Copy link
Owner

Create a gist with a config file, remove sensitive data and show me,

@sammy007
Copy link
Owner

make sure you have this param in unlocker config https://github.com/sammy007/open-ethereum-pool/blob/master/config.example.json#L3

@eug13768
Copy link
Author

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
2016/07/25 18:46:45 Mature block 1934668 with 0 tx, hash: 0xcd8cb2c7
2016/07/25 18:46:45 Mature block 1934673 with 1 tx, hash: 0x9dfd67c1
2016/07/25 18:46:46 Mature block 1934682 with 2 tx, hash: 0x62c809d7
2016/07/25 18:46:46 Mature uncle 1934719/1934718 of reward 4375000000000000000 with hash: 0xf9862a7b
2016/07/25 18:46:46 Mature block 1934723 with 0 tx, hash: 0xe630e17d
2016/07/25 18:46:46 Mature block 1934769 with 0 tx, hash: 0x4250e3d8
2016/07/25 18:46:46 Mature block 1934790 with 1 tx, hash: 0xbff45c33
2016/07/25 18:46:46 Mature block 1934833 with 0 tx, hash: 0x44318ce2
2016/07/25 18:46:46 Mature block 1934845 with 0 tx, hash: 0xc1939be4
2016/07/25 18:46:46 Mature block 1934852 with 0 tx, hash: 0xfb27f3bf

@eug13768
Copy link
Author

Please wait a second, let me run payouts.

@sammy007
Copy link
Owner

I see your blocks are now immature, let them mature now.

@sammy007
Copy link
Owner

sammy007 commented Jul 25, 2016

For payouts make sure your coinbase account is unlocked with geth --unlock '0x...' and you have enough peers on this node. This is configurable.

Account must be permanently unlocked.

@eug13768
Copy link
Author

Now it shows

Blocks: 2184 Immature: 0 New; 2

Yes, geth is running with --unlock. Anything special to add to payouts.json ("coin": "eth")?

@sammy007
Copy link
Owner

Usually configs must be equal just enabled/disable particular modules.

@eug13768
Copy link
Author

Payouts go.

Thank you for your help!

@sammy007
Copy link
Owner

Good luck with your classic pool, make sure donate: true is there.

@eug13768
Copy link
Author

It's there and will stay there - you should have some ETC when the process finish and further.

@sammy007
Copy link
Owner

I suggest you to rise payout threshold to 1 Ether otherwise your payouts will last forever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants