-
Notifications
You must be signed in to change notification settings - Fork 20.4k
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
"--bootnodes" option doesn't work (private network) #2708
Comments
I've done further investigation. Updated version to latest available in Ubuntu (instance: Geth/v1.4.7-stable/linux/go1.5.1) and bootnodes doesn't understand proper bootnode definition. I start geth with:
grep for Bootstrap shows:
Seems that geth doesn't understand spaces. In case of one bootnodes I got another error
and there is no nodes. |
;) Edit:
|
@karalabe thanks for the response. a) That means that documentation is wrong. There is nothing about ',' in here: b) doesn't explain why bootnets doesn't work when only one node is specify. Second error message about leveldb. c) adding ',' works only if there is not spaces - that very silly There is no peers (so the result is the same as with one node): |
a) Thanks, fixed. |
Thanks for update. Now, why my node doesn't see any peers? Anything I can find in debug? |
@fjl Could you please jump in with a debug log level argument to display logs pertaining to these connectivity issues? |
BTW. I bump verbosity up to 6. |
I wonder if there any relation to issue 2727. |
@karalabe there is another place with not update documentation: https://github.com/ethereum/go-ethereum/wiki/Command-Line-Options |
I see '--bootnodes' works in 1.4.11. |
I know this is closed, but I get the same problem using the ethereum/client-do Docker image. Looks like "--bootnodes" is ignored, and geth version is 1.4.11-stable. |
Wow, its over a year and I'm having the same issue.. |
today, Geth/v1.7.3-unstable/linux-amd64/go1.9.1 has the same issue. |
What doesn't work? We re constantly using this on the Rinkeby testnet and other private network too. It works. Unless you provide any details, there's no way for us to help you. |
|
Maybe each node needs its own unique datadir? I'm not 100% on that but mine have separate datadirs and a proper static-nodes.json in each datadir and they connect to each other fine. |
There are a lot of things that can go wrong here. Some things to look into are
|
Same issue here, --bootnodes not work, but adding the node with admin.addPeer(enodeurl) working, with the excat same enode url infos. the command line: ouput in verbose 6 E:\Geth>geth --identity "MyTestNodePc2" --nodiscover --bootnodes "enode://8966b7a85496bd37e61fceb49ca03c1527291d0c21dbf9a3ab68226174704e6c2a18929e748cd802f80bb0a67136950dc1fdc89c2825b4c6e7dcc35c36c51826@[::]:30303" --datadir e:/geth/node_data_testnet2 --port 30304 --rpc --rpcport 8102 --ipcdisable -verbosity 6 --mine --minerthreads 1 console TRACE[06-13|23:24:21] msg="sending {"jsonrpc":"2.0","id":2,"method":"web3_clientVersion","params":[]}"
no node added. after adding node manulay by command: admin.addPeer("enode://8966b7a85496bd37e61fceb49ca03c1527291d0c21dbf9a3ab68226174704e6c2a18929e748cd802f80bb0a67136950dc1fdc89c2825b4c6e7dcc35c36c51826@[::]:30303") it's working, so it's not an port or other things issue, --bootnodes not work ! |
Skitzo |
For info, using static nodes works, [ |
Here is a collection of scripts for running a private network using go-ethereum. For adding bootnodes, check out the scripts They will essentially start and stop each node, grabbing the enode of each and writing them to a file, |
I've this error: the file Dockerfile was specific another (different enode, the right!): enode://0df98758a40a58db0ec6c4db14f9241dcf3fec37b0bdb08720de369da0ea1631a3f55717135518a9dea25c8854554f4ccddb33c8d5402130fcbca76fe8d74249@5.189.165.78:30301 the error report an enode used in yhe past! how do fix? |
System information
Geth version: Geth/v1.3.6/linux/go1.5.1
OS & Version: Linux (Ubuntu 14.04)
Expected behaviour
Nodes specify in 'bootnodes' are added during geth start
Actual behaviour
Nodes are not added.
Steps to reproduce the behaviour
I have following command with 2 bootnodes provided, however they are not added to during boot up:
geth --genesis /geth/seed.json --bootnodes enode://[email protected]:30303 enode:/[email protected]:30303 --rpc --rpcaddr 0.0.0.0 --rpcport 8080 --rpccorsdomain * --ipcpath /geth/geth.ipc --datadir /geth/chain --port 30303 --autodag --networkid 12121212 --metrics --verbosity 5
The text was updated successfully, but these errors were encountered: