[ethereum/go-ethereum] Puppeth (for PoA bootnode) created docker image restarting always (#17434)

Hi there,

please note that this is an issue tracker reserved for bug reports and feature requests.

For general questions please use the gitter channel or the Ethereum stack exchange at https://ethereum.stackexchange.com.

#### System information

Geth version: `geth version`
OS & Version: Windows/Linux/OSX
Commit hash : (if `develop`)

#### Expected behaviour
Please specify a network name to administer (no spaces or hyphens, please)
> testpuppeth3

Sweet, you can set this via —network=testpuppeth3 next time!

INFO [08-17|20:52:24.891] Administering Ethereum network name=testpuppeth3
WARN [08-17|20:52:24.891] No previous configurations found path=/home/ubuntu/.puppeth/testpuppeth3

What would you like to do? (default = stats)
1. Show network stats
2. Configure new genesis
3. Track new remote server
4. Deploy network components
> 2

Which consensus engine to use? (default = clique)
1. Ethash — proof-of-work
2. Clique — proof-of-authority
> 2

How many seconds should blocks take? (default = 15)
> 5

Which accounts are allowed to seal? (mandatory at least one)
> 0x3cb359018604bffd282dca629aa8e4b014914331
> 0x2caa5105bedfe1e80aa1e89e5177867bf7f2fa76
> 0x

Which accounts should be pre-funded? (advisable at least one)
> 0x3cb359018604bffd282dca629aa8e4b014914331
> 0x2caa5105bedfe1e80aa1e89e5177867bf7f2fa76
> 0x581e6818f835c6b8eec86e32bd034bb69bb68e00
> 0x3d186495787760f803a64163190ec3846dd49c51
> 0x329fbc1b7db2808a9f103b5d86d2555f6831eff0
> 0x

Specify your chain/network ID if you want an explicit one (default = random)
> 700
INFO [08-17|20:53:24.859] Configured new genesis block

What would you like to do? (default = stats)
1. Show network stats
2. Manage existing genesis
3. Track new remote server
4. Deploy network components
> 4

What would you like to deploy? (recommended order)
1. Ethstats — Network monitoring tool
2. Bootnode — Entry point of the network
3. Sealer — Full node minting new blocks
4. Explorer — Chain analysis webservice (ethash only)
5. Wallet — Browser wallet for quick sends
6. Faucet — Crypto faucet to give away funds
7. Dashboard — Website listing above web-services
> 1

Which server do you want to interact with?
1. Connect another server
> 1

Please enter remote server’s address:
> x.x.x.x

The authenticity of host ‘x.x.x.x:22 (x.x.x.x:22)’ can’t be established.
SSH key fingerprint is df:89:2f:60:5a:19:00:18:1d:8f:42:74:b8:a7:38:8e [MD5]
Are you sure you want to continue connecting (yes/no)? yes

Which port should ethstats listen on? (default = 80)
> 8080

Allow sharing the port with other services (y/n)? (default = yes)
> n

What should be the secret password for the API? (must not be empty)
> PrivateTest-DockerNode2
Creating network «testpuppeth3_default» with the default driver
Building ethstats
Step 1/2 : FROM puppeth/ethstats:latest
—> fb62abe59cb2
Step 2/2 : RUN echo ‘module.exports = {trusted: [«x.x.x.x»], banned: [], reserved: [«yournode»]};’ > lib/utils/config.js
—> Using cache
—> aba8e97485df
Successfully built aba8e97485df
Successfully tagged testpuppeth3/ethstats:latest
Creating testpuppeth3_ethstats_1
INFO [08-17|20:54:29.020] Starting remote server health-check server=x.x.x.x
+—————+—————+———-+————————+————————-+
| SERVER | ADDRESS | SERVICE | CONFIG | VALUE |
+—————+—————+———-+————————+————————-+
| x.x.x.x | x.x.x.x | ethstats | Banned addresses | [] |
| | | | Login secret | PrivateTest-DockerNode2 |
| | | | Website address | x.x.x.x |
| | | | Website listener port | 8080 |
+—————+—————+———-+————————+————————-+
What would you like to do? (default = stats)
1. Show network stats
2. Manage existing genesis
3. Manage tracked machines
4. Manage network components
> 4

1. Tear down Ethstats on x.x.x.x
2. Deploy new network component
> 2

What would you like to deploy? (recommended order)
1. Ethstats — Network monitoring tool
2. Bootnode — Entry point of the network
3. Sealer — Full node minting new blocks
4. Explorer — Chain analysis webservice (ethash only)
5. Wallet — Browser wallet for quick sends
6. Faucet — Crypto faucet to give away funds
7. Dashboard — Website listing above web-services
> 2

Which server do you want to interact with?
1. x.x.x.x
2. Connect another server
> 1

Where should data be stored on the remote machine?
> /home/ubuntu/testpuppeth3/bootnode

Which TCP/UDP port to listen on? (default = 30303)
> 30305

How many peers to allow connecting? (default = 512)
>

How many light peers to allow connecting? (default = 256)
>
What should the node be called on the stats page?
> testpuppeth3_bootnode
Found orphan containers (testpuppeth3_ethstats_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the —remove-orphans flag to clean it up.
Building bootnode
Step 1/4 : FROM ethereum/client-go:latest
—> 985900870511
Step 2/4 : ADD genesis.json /genesis.json
—> 5e41a4c0a8f2
Step 3/4 : RUN echo ‘geth —cache 512 init /genesis.json’ > geth.sh && echo $’geth —networkid 700 —cache 512 —port 30305 —maxpeers 512 —lightpeers=256 —lightserv=50 —ethstats \’testpuppeth3_bootnode:PrivateTest-DockerNode2@x.x.x.x:8080\’ —targetgaslimit 0 —gasprice 0′ >> geth.sh
—> Running in 56bd4b9d6e26
Removing intermediate container 56bd4b9d6e26
—> b13cde356c8d
Step 4/4 : ENTRYPOINT [«/bin/sh», «geth.sh»]
—> Running in 6ff777398881
Removing intermediate container 6ff777398881
—> 2f3e2408fbf6
Successfully built 2f3e2408fbf6
Successfully tagged testpuppeth3/bootnode:latest
Creating testpuppeth3_bootnode_1
INFO [08-17|20:56:02.659] Waiting for node to finish booting
INFO [08-17|20:56:05.659] Starting remote server health-check server=13.58.151.81
+—————+—————+———-+————————+————————-+
| SERVER | ADDRESS | SERVICE | CONFIG | VALUE |
+—————+—————+———-+————————+————————-+
| x.x.x.x | x.x.x.x | bootnode | offline | service unreachable |
| | | | ——————— | ———————— |
| | | ethstats | Banned addresses | [] |
| | | | Login secret | PrivateTest-DockerNode2 |
| | | | Website address | x.x.x.x |
| | | | Website listener port | 8080 |
+—————+—————+———-+————————+————————-+
#### Actual behaviour
On the server-side @x.x.x.x
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
76cdd0a6e2cd testpuppeth3/bootnode «/bin/sh geth.sh» 11 minutes ago Restarting (2) 11 seconds ago testpuppeth3_bootnode_1
08b10ae8081f testpuppeth3/ethstats «npm start» 21 minutes ago Up 21 minutes 0.0.0.0:8080->3000/tcp testpuppeth3_ethstats_1
****Few Minutes Later…*****
$docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
76cdd0a6e2cd testpuppeth3/bootnode «/bin/sh geth.sh» 24 minutes ago Restarting (2) 10 seconds ago testpuppeth3_bootnode_1
08b10ae8081f testpuppeth3/ethstats «npm start» 34 minutes ago Up 34 minutes
#### Steps to reproduce the behaviour

#### Backtrace

««
[backtrace]
««
1. I get the same behaviour for creating sealer nodes on another server.
2. Why does the boot node or the seal node docker container issued by puppeth for PoA setup crashes and is in an infinite loop to restart?

Am I doing anything wrong here? Did I get the eth-stats setup right?

Please help, thanks
Karthika

Добавить комментарий