search

openethereum / parity-deploy

Parity deployment script.
Apache License 2.0
81 stars 52 forks source link

libstdc++.so.6: version `GLIBCXX_3.4.22' not found #51

Closed drandreaskrueger closed 6 years ago

drandreaskrueger commented 6 years ago

Problem

nodes are not there.

yes http://localhost:3001/ comes up - but bottom half of the page is empty

and no answer on :8545

curl -X POST --data '{"jsonrpc":"2.0","method":"net_version","params":[],"id":67}' -H "Content-Type: application/json" localhost:8545
curl: (7) Failed to connect to localhost port 8545: Connection refused

How to replicate the problem:

happened with commit 57267338cb7b2003a0322408dc4daeedfaf88e53

git clone https://github.com/paritytech/parity-deploy paritytech_parity-deploy
cd paritytech_parity-deploy/
./parity-deploy.sh --config aura --name myaura --nodes 4 --ethstats

read EC key
read EC key
read EC key
read EC key
docker-compose up

Recreating host1                              ... done
Recreating host3                              ... done
Recreating host2                              ... done
Recreating host4                              ... done
Starting paritytech_parity-deploy_dashboard_1 ... done
Starting paritytech_parity-deploy_monitor_1   ... done
Attaching to paritytech_parity-deploy_dashboard_1, paritytech_parity-deploy_monitor_1, host4, host2, host1, host3
dashboard_1  | npm info it worked if it ends with ok
dashboard_1  | npm info using npm@4.1.2
dashboard_1  | npm info using node@v7.7.3
dashboard_1  | npm info lifecycle eth-netstats@0.0.9~prestart: eth-netstats@0.0.9
dashboard_1  | npm info lifecycle eth-netstats@0.0.9~start: eth-netstats@0.0.9
dashboard_1  | 
dashboard_1  | > eth-netstats@0.0.9 start /eth-netstats
monitor_1    | [PM2] Spawning PM2 daemon with pm2_home=/home/ethnetintel/.pm2
dashboard_1  | > node ./bin/www
host4        | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
dashboard_1  | 
monitor_1    | [PM2] PM2 Successfully daemonized
monitor_1    | [PM2][WARN] Applications host1, host2, host3 not running, starting...
host2        | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
monitor_1    | [PM2] App [host1] launched (1 instances)
monitor_1    | [PM2] App [host2] launched (1 instances)
monitor_1    | [PM2] App [host3] launched (1 instances)
monitor_1    | ┌──────────┬────┬──────┬─────┬────────┬─────────┬────────┬─────┬───────────┬──────────┐
monitor_1    | │ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ mem       │ watching │
host1        | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
monitor_1    | ├──────────┼────┼──────┼─────┼────────┼─────────┼────────┼─────┼───────────┼──────────┤
monitor_1    | │ host1    │ 0  │ fork │ 17  │ online │ 0       │ 0s     │ 81% │ 22.9 MB   │ enabled  │
monitor_1    | │ host2    │ 1  │ fork │ 21  │ online │ 0       │ 0s     │ 85% │ 26.1 MB   │ enabled  │
monitor_1    | │ host3    │ 2  │ fork │ 28  │ online │ 0       │ 0s     │ 87% │ 26.8 MB   │ enabled  │
monitor_1    | └──────────┴────┴──────┴─────┴────────┴─────────┴────────┴─────┴───────────┴──────────┘
host4 exited with code 1
host3        | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host1 exited with code 1
monitor_1    |  Use `pm2 show <id|name>` to get more details about an app
monitor_1    | tail: unrecognized file system type 0x794c7630 for '/home/ethnetintel/.pm2/logs/node-app-out-0.log'. please report this to bug-coreutils@gnu.org. reverting to polling
host2 exited with code 1
host3 exited with code 1

Ctrl-C

^CGracefully stopping... (press Ctrl+C again to force)
Stopping paritytech_parity-deploy_monitor_1   ... done
Stopping paritytech_parity-deploy_dashboard_1 ... done
drandreaskrueger commented 6 years ago

simpler:

./parity-deploy.sh --config aura --name myaura --nodes 4

read EC key
read EC key
read EC key
read EC key
docker-compose up

Starting host3 ... done
Starting host4 ... done
Starting host2 ... done
Starting host1 ... done
Attaching to host3, host1, host2, host4
host3    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host1    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host2    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host4    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host3 exited with code 1
host1 exited with code 1
host2 exited with code 1
host4 exited with code 1
drandreaskrueger commented 6 years ago

In the docker-compose.yml I have also tried to manually replace 

image: parity/parity:stable

with 

image: parity/parity:v1.11.7

but then it gets worse:

docker-compose up
Starting host4 ... done
Starting host3 ... done
Starting host2 ... done
Starting host1 ... done
Attaching to host4, host3, host1, host2
host4    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /parity/parity)
host4    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host4    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /parity/parity)
host4    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /parity/parity)
host1    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /parity/parity)
host1    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host3    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /parity/parity)
host3    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host3    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /parity/parity)
host3    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /parity/parity)
host1    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /parity/parity)
host1    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /parity/parity)
host2    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /parity/parity)
host2    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host2    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /parity/parity)
host2    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /parity/parity)
host4 exited with code 1
host3 exited with code 1
host2 exited with code 1
host1 exited with code 1

even more libraries missing

drandreaskrueger commented 6 years ago

simplest way to recreate the problem:

./parity-deploy.sh --config aura
docker-compose up
Recreating host1 ... done
Attaching to host1
host1    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host1 exited with code 1
drandreaskrueger commented 6 years ago

same when I replace 

image: parity/parity:stable

with

image: parity/parity:beta

--> 

./parity-deploy.sh --config aura --name myaura --nodes 4 
gedit docker-compose.yml 
docker-compose up
Starting host1 ... done
Starting host4 ... done
Starting host3 ... done
Starting host2 ... done
Attaching to host3, host1, host4, host2
host3    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host1    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host4    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host2    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host1 exited with code 1
host3 exited with code 1
host4 exited with code 1
host2 exited with code 1
drandreaskrueger commented 6 years ago

Why all this?
I do not want to repair your docker problems, but simply benchmark parity PoA, to be able to compare it with e.g. quorum IBFT and geth Clique (see my chainhammer tools & results); and I need some simplistic multi-node PoA network for that.

Instead, I am going to benchmark with https://github.com/orbita-center/parity-poa-playground now. That is working: http://localhost:3001/ shows 6 nodes, and :8545 is answering:

curl -X POST --data '{"jsonrpc":"2.0","method":"net_version","params":[],"id":67}' -H "Content-Type: application/json" localhost:8545  
{"jsonrpc":"2.0","result":"8995","id":67}

And it is on version v1.11.8-stable-92776e4-20180728

Thanks anyways.

ddorgan commented 6 years ago

Strange. What o/s and version are you using??

For example on a clean ubuntu 16 system using the command ./parity-deploy.sh --config aura --name myaura --nodes 4 --ethstats I get:


root@ov1:/tmp/paritytech_parity-deploy# docker-compose  up
Starting paritytechparitydeploy_dashboard_1 ... 
Starting paritytechparitydeploy_monitor_1 ... 
Starting paritytechparitydeploy_dashboard_1
Starting paritytechparitydeploy_monitor_1
Starting host4 ... 
Starting host4
Creating host1 ... 
Starting paritytechparitydeploy_monitor_1 ... done
Creating host3 ... 
Starting paritytechparitydeploy_dashboard_1 ... done
Creating host3
Starting host4 ... done
Attaching to paritytechparitydeploy_monitor_1, paritytechparitydeploy_dashboard_1, host1, host3, host2, host4
monitor_1    | [PM2] Spawning PM2 daemon with pm2_home=/home/ethnetintel/.pm2
monitor_1    | [PM2] PM2 Successfully daemonized
monitor_1    | [PM2][WARN] Applications host1, host2, host3 not running, starting...
monitor_1    | [PM2] App [host1] launched (1 instances)
monitor_1    | [PM2] App [host2] launched (1 instances)
monitor_1    | [PM2] App [host3] launched (1 instances)
monitor_1    | ┌──────────┬────┬──────┬─────┬────────┬─────────┬────────┬─────┬───────────┬──────────┐
monitor_1    | │ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ mem       │ watching │
monitor_1    | ├──────────┼────┼──────┼─────┼────────┼─────────┼────────┼─────┼───────────┼──────────┤
monitor_1    | │ host1    │ 0  │ fork │ 16  │ online │ 0       │ 0s     │ 61% │ 16.5 MB   │ enabled  │
monitor_1    | │ host2    │ 1  │ fork │ 20  │ online │ 0       │ 0s     │ 56% │ 20.3 MB   │ enabled  │
monitor_1    | │ host3    │ 2  │ fork │ 25  │ online │ 0       │ 0s     │ 27% │ 15.6 MB   │ enabled  │
monitor_1    | └──────────┴────┴──────┴─────┴────────┴─────────┴────────┴─────┴───────────┴──────────┘
monitor_1    |  Use `pm2 show <id|name>` to get more details about an app
dashboard_1  | npm info it worked if it ends with ok
dashboard_1  | npm info using npm@4.1.2
dashboard_1  | npm info using node@v7.7.3
dashboard_1  | npm info lifecycle eth-netstats@0.0.9~prestart: eth-netstats@0.0.9
dashboard_1  | npm info lifecycle eth-netstats@0.0.9~start: eth-netstats@0.0.9
dashboard_1  | 
dashboard_1  | > eth-netstats@0.0.9 start /eth-netstats
dashboard_1  | > node ./bin/www
dashboard_1  | 
host1        | Loading config file from /parity/authority.toml
host1        | 2018-08-21 16:17:41 UTC Starting Parity/v1.11.8-stable-c754a02-20180725/x86_64-linux-gnu/rustc1.27.2
host1        | 2018-08-21 16:17:41 UTC Keys path /parity/data/keys/myaura
host1        | 2018-08-21 16:17:41 UTC DB path /parity/data/chains/myaura/db/0796728f28a12423
host1        | 2018-08-21 16:17:41 UTC Path to dapps /parity/data/dapps
host1        | 2018-08-21 16:17:41 UTC State DB configuration: fast
host1        | 2018-08-21 16:17:41 UTC Operating mode: active
host3        | Loading config file from /parity/authority.toml
host3        | 2018-08-21 16:17:41 UTC Starting Parity/v1.11.8-stable-c754a02-20180725/x86_64-linux-gnu/rustc1.27.2
host3        | 2018-08-21 16:17:41 UTC Keys path /parity/data/keys/myaura
host3        | 2018-08-21 16:17:41 UTC DB path /parity/data/chains/myaura/db/0796728f28a12423
host3        | 2018-08-21 16:17:41 UTC Path to dapps /parity/data/dapps
host3        | 2018-08-21 16:17:41 UTC State DB configuration: fast
host3        | 2018-08-21 16:17:41 UTC Operating mode: active
host2        | Loading config file from /parity/authority.toml
host2        | 2018-08-21 16:17:41 UTC Starting Parity/v1.11.8-stable-c754a02-20180725/x86_64-linux-gnu/rustc1.27.2
host2        | 2018-08-21 16:17:41 UTC Keys path /parity/data/keys/myaura
host2        | 2018-08-21 16:17:41 UTC DB path /parity/data/chains/myaura/db/0796728f28a12423
host2        | 2018-08-21 16:17:41 UTC Path to dapps /parity/data/dapps
host2        | 2018-08-21 16:17:41 UTC State DB configuration: fast
host2        | 2018-08-21 16:17:41 UTC Operating mode: active
host4        | Loading config file from /parity/authority.toml
host1        | 2018-08-21 16:17:41 UTC Configured for myaura using AuthorityRound engine
host4        | 2018-08-21 16:17:41 UTC Starting Parity/v1.11.8-stable-c754a02-20180725/x86_64-linux-gnu/rustc1.27.2
host4        | 2018-08-21 16:17:41 UTC Keys path /parity/data/keys/myaura
host4        | 2018-08-21 16:17:41 UTC DB path /parity/data/chains/myaura/db/0796728f28a12423
host4        | 2018-08-21 16:17:41 UTC Path to dapps /parity/data/dapps
host4        | 2018-08-21 16:17:41 UTC State DB configuration: fast
host4        | 2018-08-21 16:17:41 UTC Operating mode: active
host3        | 2018-08-21 16:17:41 UTC Configured for myaura using AuthorityRound engine
host2        | 2018-08-21 16:17:41 UTC Configured for myaura using AuthorityRound engine
host4        | 2018-08-21 16:17:41 UTC Configured for myaura using AuthorityRound engine
dashboard_1  | 2018-08-21 16:17:42.446 [API] [CON] Connected host2
dashboard_1  | 2018-08-21 16:17:42.467 [API] [CON] Connected host3
dashboard_1  | 2018-08-21 16:17:42.471 [API] [BLK] Block error: Block undefined
dashboard_1  | 2018-08-21 16:17:42.475 [API] [STA] Stats from: host2
dashboard_1  | 2018-08-21 16:17:42.484 [API] [BLK] Block error: Block undefined
dashboard_1  | 2018-08-21 16:17:42.486 [API] [CON] Connected host1
dashboard_1  | 2018-08-21 16:17:42.489 [API] [STA] Stats from: host3
dashboard_1  | 2018-08-21 16:17:42.506 [API] [BLK] Block error: Block undefined
dashboard_1  | 2018-08-21 16:17:42.517 [API] [STA] Stats from: host1
dashboard_1  | 2018-08-21 16:17:45.428 [API] [CON] Connection with: MLTHmuS ended: undefined
dashboard_1  | 2018-08-21 16:17:46.401 [API] [CON] Connected host2
dashboard_1  | 2018-08-21 16:17:46.427 [API] [BLK] Block error: Block undefined
dashboard_1  | 2018-08-21 16:17:46.435 [API] [STA] Stats from: host2
host1        | 2018-08-21 16:17:46 UTC Public node URL: enode://61cb5a084517c04ddc0e66c3059a365329fef7aa14b232f367c15245b5dc63b372bb6be4ad6cb41e27631616e867cdc465a4c106c5070ee71e943769dffb2577@172.19.0.5:30303
host3        | 2018-08-21 16:17:46 UTC Public node URL: enode://14ba51ff39bbebecbe386f8a25457defd37e716e694d0c7b865c941ac6dc87656686a5ad93e0bacce7c997402f5a5fa061ba9b43f351f2da117f371c57e61a9e@172.19.0.7:30303
host2        | 2018-08-21 16:17:46 UTC Public node URL: enode://bf1e5c1cff03d0205282f716514e3a6afb5ce66d0354787bb665a09214302c656eb2c11f85498fe9c85bac7d5958be4c24d486e6c29d146cb720a42a229856ff@172.19.0.6:30303
host4        | 2018-08-21 16:17:46 UTC Public node URL: enode://d88d35f97226d1385ed7911b9c7c1388f9d4c3c21345c3dfc494d5e3450d12af9a81e3055e296f5aff174291fd768971601ce3a5230ac8c38574bdfa850e60a4@172.19.0.4:30303
dashboard_1  | 2018-08-21 16:17:52.451 [API] [STA] Stats from: host3
dashboard_1  | 2018-08-21 16:17:52.456 [API] [STA] Stats from: host1
dashboard_1  | 2018-08-21 16:17:56.386 [API] [STA] Stats from: host2
host3        | 2018-08-21 16:18:11 UTC    3/25 peers      8 KiB chain    7 KiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  2 req/s, 136 µs
host2        | 2018-08-21 16:18:11 UTC    3/25 peers      8 KiB chain    7 KiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  2 req/s, 166 µs
host4        | 2018-08-21 16:18:11 UTC    3/25 peers      8 KiB chain    7 KiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
host1        | 2018-08-21 16:18:16 UTC    3/25 peers      8 KiB chain    7 KiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  3 req/s, 126 µs
host3        | 2018-08-21 16:18:41 UTC    3/25 peers      8 KiB chain    7 KiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  2 req/s, 104 µs
host2        | 2018-08-21 16:18:41 UTC    3/25 peers      8 KiB chain    7 KiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  2 req/s, 138 µs
host4        | 2018-08-21 16:18:41 UTC    3/25 peers      8 KiB chain    7 KiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
host1        | 2018-08-21 16:18:46 UTC    3/25 peers      8 KiB chain    7 KiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  3 req/s, 132 µs
drandreaskrueger commented 6 years ago

What o/s and version are you using??

Debian Linux

uname -a
Linux ... 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) x86_64 GNU/Linux

Parity Version v1.11.8-stable-92776e4-20180728

docker-compose version
docker-compose version 1.21.1, build 5a3f1a3
docker-py version: 3.3.0
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.1.0f  25 May 2017
docker version
Client:
 Version:           18.06.0-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        0ffa825
 Built:             Wed Jul 18 19:09:33 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.0-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       0ffa825
  Built:            Wed Jul 18 19:07:38 2018
  OS/Arch:          linux/amd64
  Experimental:     false

any other version that I could look up for you?

ddorgan commented 6 years ago

Yes, what's the output of /usr/bin/parity --version (on the docker host, not the container).

I setup a new debian host from scratch and don't seem to have the same issue. Here's some version info:

Newly installed debian host:

# uname -a
Linux tmp-debian 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) x86_64 GNU/Linux
# docker-compose  --version
docker-compose version 1.8.0, build unknown
# openssl version
OpenSSL 1.1.0f  25 May 2017

Docker info:

Client:
 Version:           18.06.0-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        0ffa825
 Built:             Wed Jul 18 19:09:33 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.0-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       0ffa825
  Built:            Wed Jul 18 19:07:38 2018
  OS/Arch:          linux/amd64
  Experimental:     false

Could you run docker run --entrypoint "ldd /parity/parity" parity/parity:stable and send the output of ldd /parity/parity ...

Very interested in helping out as it may make things easier to tweak with your benchmarks and the other issue you have open in the parity-ethereum repo.

Thanks!

drandreaskrueger commented 6 years ago

I am back at that machine on Tuesday & Wednesday, then I can try more things.

Right now, and from remote, I suspect that the host system parity is an older version, and that is (hopefully) causing these problems.

(Actually, could you modify parity-deploy.sh to not use any other parity binary but the dockerized one? I.e. the same parity that is then called via docker-compose.yml - that way, you could avoid version mismatch problems.)

Thanks A LOT for being so helpful & responsive. Much appreciated!

drandreaskrueger commented 6 years ago

modify parity-deploy.sh to not use any other parity binary but the dockerized one

anyways, this was my host system parity:

which parity
/usr/bin/parity
/usr/bin/parity --version
Parity/v1.10.6-stable-bc0d134bb-20180605/x86_64-linux-gnu/rustc1.26.1
drandreaskrueger commented 6 years ago

Updated it: 

wget https://releases.parity.io/v1.11.8/x86_64-unknown-debian-gnu/parity_1.11.8_debian_amd64.deb
sudo gdebi parity_1.11.8_debian_amd64.deb 
... Unpacking parity (1.11.8) over (1.10.6) ...

/usr/bin/parity --version
Parity/v1.11.8-stable-c754a028e-20180725/x86_64-linux-gnu/rustc1.27.2
drandreaskrueger commented 6 years ago

New attempt, all from scratch:

git clone https://github.com/paritytech/parity-deploy.git paritytech_parity-deploy
cd paritytech_parity-deploy

git log
commit ab1a0e6162de656f4737a76dd547efbac4e46fe4
Merge: 5726733 5b24deb
Author: ddorgan <david@peersystems.co.uk>
Date:   Tue Aug 21 18:24:36 2018 +0200
docker kill $(docker ps -q); docker rm $(docker ps -a -q); docker rmi $(docker images -q)
drandreaskrueger commented 6 years ago 
./parity-deploy.sh --config aura
read EC key
docker-compose up
Pulling host1 (parity/parity:stable)...
[...]
Digest: sha256:1235d839a171e862e4d4cb7e846f99f681a085caab4f6f7cd937032e16033727
Status: Downloaded newer image for parity/parity:stable
Creating host1 ... done
Attaching to host1

host1    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)

host1 exited with code 1

Nope, sorry.

Broken.

drandreaskrueger commented 6 years ago

Is parity/parity:stable the docker image your tool is using too?

By itself it runs without problems:

docker run parity/parity:stable
2018-08-29 09:00:16 UTC Starting Parity/v1.11.8-stable-92776e4-20180728/x86_64-linux-gnu/rustc1.27.2
2018-08-29 09:00:16 UTC Keys path /root/.local/share/io.parity.ethereum/keys/Foundation
2018-08-29 09:00:16 UTC DB path /root/.local/share/io.parity.ethereum/chains/ethereum/db/906a34e69aec8c0d
2018-08-29 09:00:16 UTC Path to dapps /root/.local/share/io.parity.ethereum/dapps
2018-08-29 09:00:16 UTC State DB configuration: fast
2018-08-29 09:00:16 UTC Operating mode: active
2018-08-29 09:00:16 UTC Configured for Foundation using Ethash engine
2018-08-29 09:00:17 UTC Updated conversion rate to Ξ1 = US$292.79 (16263890 wei/gas)
2018-08-29 09:00:21 UTC Public node URL: enode://21a7767bd0ede897b8b44fe28c2e3d5f72dea7235a6123c513dc1c2d2c79538860d49b287a772220f8112da9d4b3cd84d1a13aa33a3919798f14ea9a1d46a216@172.17.0.2:30303
^C2018-08-29 09:00:24 UTC Finishing work, please wait...
drandreaskrueger commented 6 years ago

what can I try out for you, to help you debugging this bug?

Would it lead anywhere if we somehow isolate the problem?

How would I call docker manually and directly, without docker-compose?

Somehow like this?

cd paritytech_parity-deploy/deployment/1
docker run parity/parity:stable --chain /parity/spec.json --config /parity/authority.toml -d data

But then I get a

There was an error reading your config file at: /parity/authority.toml
Config doesn't match any presets [dev, mining, non-standard-ports, insecure, dev-insecure]
drandreaskrueger commented 6 years ago

OR:

Does one of these help you to find out where this bug might come from?

ddorgan commented 6 years ago

Oh ok ... so parity/parity:stable runs ok by itself but when you ready docker-compose up you have issues?

Can you wipe the data dir and tar up the whole thing and let me take a look, please?

ddorgan commented 6 years ago

BTW, not sure why you are seeing:

Status: Downloaded newer image for parity/parity:stable

You already had the v1.10.8-stable version, right?? No weird permissions issues there?

ddorgan commented 6 years ago

BTW, you have tried this on a clean system right? There's nothing really funky with your setup in general? :-)

The reason I'm asking is I did deploy a fresh debian system and didn't see these issues myself....

drandreaskrueger commented 6 years ago

BTW, you have tried this on a clean system right?

No, this is the machine on which I am typing this.

Installed in 2016 if I remember correctly. But it's working just fine.

There's nothing really funky with your setup in general? :-)

Nope. All good. And with none of the benchmarked systems (log.md, quorum.md, tobalaba.md, quorum-IBFT.md in chainhammer) I have had any such problems.

but thi problem is not unknown and also not in relation to parity - something's wrong with linking of some libraries. Where exactly could that be caused?

`GLIBCXX_3.4.22' not found

where in parity that gets linked?

(required by /parity/parity)

where in parity is that required?

Oh ok ... so parity/parity:stable runs ok by itself but when you ready docker-compose up you have issues?

Yes, exactly.

Odd.

What is a smallest possible docker-compose.yml file which would just start parity, similar to docker run parity/parity:stable, so that I could try to isolate your problem?

Can you wipe the data dir and tar up the whole thing and let me take a look, please?

Yes, done this:

sudo ./clean.sh

./parity-deploy.sh --config aura
read EC key

docker-compose up
Starting host1 ... done
Attaching to host1
host1    | /parity/parity: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /parity/parity)
host1 exited with code 1

I don't have to wipe anything by the way, the data folder is empty, only folders:

ls -laR data
data:
total 12
drwxr-xr-x  3 root     root     4096 Aug 29 15:07 .
drwxr-xr-x 11 akrueger akrueger 4096 Aug 29 15:07 ..
drwxr-xr-x  3 root     root     4096 Aug 29 15:07 1

data/1:
total 12
drwxr-xr-x 3 root root 4096 Aug 29 15:07 .
drwxr-xr-x 3 root root 4096 Aug 29 15:07 ..
drwxr-xr-x 3 root root 4096 Aug 29 15:07 keys

data/1/keys:
total 12
drwxr-xr-x 3 root root 4096 Aug 29 15:07 .
drwxr-xr-x 3 root root 4096 Aug 29 15:07 ..
drwxr-xr-x 2 root root 4096 Aug 29 15:07 parity

data/1/keys/parity:
total 8
drwxr-xr-x 2 root root 4096 Aug 29 15:07 .
drwxr-xr-x 3 root root 4096 Aug 29 15:07 ..

but here is the archive, attached.

paritytech_parity-deploy_Andreas.zip

drandreaskrueger commented 6 years ago

not sure why you are seeing:
Status: Downloaded newer image for parity/parity:stable

probably because of the prior

docker kill $(docker ps -q); docker rm $(docker ps -a -q); docker rmi $(docker images -q)

I wiped everything to have a clean as possible system. What else could I do in that direction?

ddorgan commented 6 years ago

@drandreaskrueger thanks for the zip, will take a look.

BTW, can you add one option to parity.....add --force-direct this will use the binary in docker and not allow it to redirect to any update.

Will let you know how I get on with the zip.

ddorgan commented 6 years ago

Please remove this from the docker-compose.yml:

       - /usr/bin/parity:/parity/parity
drandreaskrueger commented 6 years ago

Please remove this from the docker-compose.yml:

  • /usr/bin/parity:/parity/parity

hooray

that's it.

Doing that manually now, but please push an update to your repo, thanks.

ddorgan commented 6 years ago

Merged: https://github.com/paritytech/parity-deploy/pull/54

Will look into your other ticket now and maybe suggest some option changes.

drandreaskrueger commented 6 years ago

just to understand where this bug came from:

you were using the wrong parity binary, right?

the one from the host machine, instead of the dockerized one.

Correct?

ddorgan commented 6 years ago

Yes, made two steps forward and one step back. This was only introduced about a week ago :/