Giter Site home page Giter Site logo

parity-deploy's Introduction

OpenEthereum

Fast and feature-rich multi-network Ethereum client.

» Download the latest release «

GPL licensed Build Status Discord chat

Table of Contents

  1. Description
  2. Technical Overview
  3. Building
    3.1 Building Dependencies
    3.2 Building from Source Code
    3.3 Starting OpenEthereum
  4. Testing
  5. Documentation
  6. Toolchain
  7. Contributing
  8. License

1. Description

Built for mission-critical use: Miners, service providers, and exchanges need fast synchronisation and maximum uptime. OpenEthereum provides the core infrastructure essential for speedy and reliable services.

  • Clean, modular codebase for easy customisation
  • Advanced CLI-based client
  • Minimal memory and storage footprint
  • Synchronise in hours, not days with Warp Sync
  • Modular for light integration into your service or product

2. Technical Overview

OpenEthereum's goal is to be the fastest, lightest, and most secure Ethereum client. We are developing OpenEthereum using the Rust programming language. OpenEthereum is licensed under the GPLv3 and can be used for all your Ethereum needs.

By default, OpenEthereum runs a JSON-RPC HTTP server on port :8545 and a Web-Sockets server on port :8546. This is fully configurable and supports a number of APIs.

If you run into problems while using OpenEthereum, check out the old wiki for documentation, feel free to file an issue in this repository, or hop on our Discord chat room to ask a question. We are glad to help!

You can download OpenEthereum's latest release at the releases page or follow the instructions below to build from source. Read the CHANGELOG.md for a list of all changes between different versions.

3. Building

3.1 Build Dependencies

OpenEthereum requires latest stable Rust version to build.

We recommend installing Rust through rustup. If you don't already have rustup, you can install it like this:

  • Linux:

    $ curl https://sh.rustup.rs -sSf | sh

    OpenEthereum also requires clang (>= 9.0), clang++, pkg-config, file, make, and cmake packages to be installed.

  • OSX:

    $ curl https://sh.rustup.rs -sSf | sh

    clang is required. It comes with Xcode command line tools or can be installed with homebrew.

  • Windows: Make sure you have Visual Studio 2015 with C++ support installed. Next, download and run the rustup installer from https://static.rust-lang.org/rustup/dist/x86_64-pc-windows-msvc/rustup-init.exe, start "VS2015 x64 Native Tools Command Prompt", and use the following command to install and set up the msvc toolchain:

    $ rustup default stable-x86_64-pc-windows-msvc

Once you have rustup installed, then you need to install:

Make sure that these binaries are in your PATH. After that, you should be able to build OpenEthereum from source.

3.2 Build from Source Code

# download OpenEthereum code
$ git clone https://github.com/openethereum/openethereum
$ cd openethereum

# build in release mode
$ cargo build --release --features final

This produces an executable in the ./target/release subdirectory.

Note: if cargo fails to parse manifest try:

$ ~/.cargo/bin/cargo build --release

Note, when compiling a crate and you receive errors, it's in most cases your outdated version of Rust, or some of your crates have to be recompiled. Cleaning the repository will most likely solve the issue if you are on the latest stable version of Rust, try:

$ cargo clean

This always compiles the latest nightly builds. If you want to build stable, do a

$ git checkout stable

3.3 Starting OpenEthereum

Manually

To start OpenEthereum manually, just run

$ ./target/release/openethereum

so OpenEthereum begins syncing the Ethereum blockchain.

Using systemd service file

To start OpenEthereum as a regular user using systemd init:

  1. Copy ./scripts/openethereum.service to your systemd user directory (usually ~/.config/systemd/user).
  2. Copy release to bin folder, write sudo install ./target/release/openethereum /usr/bin/openethereum
  3. To configure OpenEthereum, see our wiki for details.

4. Testing

Download the required test files: git submodule update --init --recursive. You can run tests with the following commands:

  • All packages

    cargo test --all
    
  • Specific package

    cargo test --package <spec>
    

Replace <spec> with one of the packages from the package list (e.g. cargo test --package evmbin).

You can show your logs in the test output by passing --nocapture (i.e. cargo test --package evmbin -- --nocapture)

5. Documentation

Be sure to check out our wiki for more information.

Viewing documentation for OpenEthereum packages

You can generate documentation for OpenEthereum Rust packages that automatically opens in your web browser using rustdoc with Cargo (of the The Rustdoc Book), by running the the following commands:

  • All packages

    cargo doc --document-private-items --open
    
  • Specific package

    cargo doc --package <spec> -- --document-private-items --open
    

Use--document-private-items to also view private documentation and --no-deps to exclude building documentation for dependencies.

Replacing <spec> with one of the following from the details section below (i.e. cargo doc --package openethereum --open):

Package List

  • OpenEthereum Client Application
    openethereum
  • OpenEthereum Account Management, Key Management Tool, and Keys Generator
    ethcore-accounts, ethkey-cli, ethstore, ethstore-cli
  • OpenEthereum Chain Specification
    chainspec
  • OpenEthereum CLI Signer Tool & RPC Client
    cli-signer parity-rpc-client
  • OpenEthereum Ethash & ProgPoW Implementations
    ethash
  • EthCore Library
    ethcore
    • OpenEthereum Blockchain Database, Test Generator, Configuration, Caching, Importing Blocks, and Block Information
      ethcore-blockchain
    • OpenEthereum Contract Calls and Blockchain Service & Registry Information
      ethcore-call-contract
    • OpenEthereum Database Access & Utilities, Database Cache Manager
      ethcore-db
    • OpenEthereum Virtual Machine (EVM) Rust Implementation
      evm
    • OpenEthereum Light Client Implementation
      ethcore-light
    • Smart Contract based Node Filter, Manage Permissions of Network Connections
      node-filter
    • OpenEthereum Client & Network Service Creation & Registration with the I/O Subsystem
      ethcore-service
    • OpenEthereum Blockchain Synchronization
      ethcore-sync
    • OpenEthereum Common Types
      common-types
    • OpenEthereum Virtual Machines (VM) Support Library
      vm
    • OpenEthereum WASM Interpreter
      wasm
    • OpenEthereum WASM Test Runner
      pwasm-run-test
    • OpenEthereum EVM Implementation
      evmbin
    • OpenEthereum JSON Deserialization
      ethjson
    • OpenEthereum State Machine Generalization for Consensus Engines
      parity-machine
  • OpenEthereum Miner Interface
    ethcore-miner parity-local-store price-info ethcore-stratum using_queue
  • OpenEthereum Logger Implementation
    ethcore-logger
  • OpenEthereum JSON-RPC Servers
    parity-rpc
  • OpenEthereum Updater Service
    parity-updater parity-hash-fetch
  • OpenEthereum Core Libraries (util)
    accounts-bloom blooms-db dir eip-712 fake-fetch fastmap fetch ethcore-io
    journaldb keccak-hasher len-caching-lock memory-cache memzero
    migration-rocksdb ethcore-network ethcore-network-devp2p panic_hook
    patricia-trie-ethereum registrar rlp_compress stats
    time-utils triehash-ethereum unexpected parity-version

6. Toolchain

In addition to the OpenEthereum client, there are additional tools in this repository available:

  • evmbin - OpenEthereum EVM Implementation.
  • ethstore - OpenEthereum Key Management.
  • ethkey - OpenEthereum Keys Generator.

The following tools are available in a separate repository:

  • ethabi - OpenEthereum Encoding of Function Calls. Docs here
  • whisper - OpenEthereum Whisper-v2 PoC Implementation.

7. Contributing

An introduction has been provided in the "So You Want to be a Core Developer" presentation slides by Hernando Castano. Additional guidelines are provided in CONTRIBUTING.

Contributor Code of Conduct

CODE_OF_CONDUCT

8. License

LICENSE

parity-deploy's People

Contributors

0x7cfe avatar 5chdn avatar barrymac avatar ddorgan avatar gitsparky avatar jwasinger avatar lopezm94 avatar office-julia avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

parity-deploy's Issues

Unable to connect ethstats

Hi all,
I am trying to deploy a network of 3 peers with ethstats.
I entered these commands:

./clean.sh
docker-compose down 
./parity-deploy.sh --config aura --nodes 3 --ethstats
docker-compose up -d

Then, when I go to the page "http://localhost:3001/", i don't see my nodes. Is there a problem with ethstats config of parity deploy ?

Thanks !

Parity dashboard works only partially

I've just installed parity on a VM instance in Google, and I can't seem to get fully working. It's somewhat partially working though.

image
(the ip on the screenshot is fake)

Note the red path to config in the top right – does this indicate something is wrong?

I've made sure these ports are exposed publicly (without them the entire thing would not be available at all):
image

My parity version is v1.9.2-beta-b60511e-20180214/x86_64-linux-gnu/rustc1.23.0.

Am I not configuring some things right? From looking at the client server logs by means of docker-compose -f logs, I can't see anything suspicious.

Ethstats Dashboard throws continuously the message "Connection with: XXXX ended: undefined"

Hi there,

I've setup my private network using:

./parity-deploy.sh --config aura --nodes 3 --ethstats

Everything looks ok, but if I check the logs with the next command:

docker-compose logs -f

I can see that Ethstats Dashboard throws continously the message:

"Connection with: XXXX ended: undefined"

Where XXXX is a random token.

Apart of this, I can see at Ethstats Dashboard that the hosts turn to gray randomly. I don't know if this is normal.

issue-parity-deploy

Please, find attached the log:

host1        | 2018-09-12 15:42:50 UTC    2/25 peers     90 KiB chain   17 KiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    1 req/s,  124 µs
dashboard_1  | 2018-09-12 15:42:50.790 [API] [CON] Connected host1
dashboard_1  | 2018-09-12 15:42:50.801 [API] [BLK] Block: 84 from: host1
dashboard_1  | 2018-09-12 15:42:50.807 [API] [STA] Stats from: host1
dashboard_1  | 2018-09-12 15:42:50.925 [API] [HIS] Got history from: host1
dashboard_1  | 2018-09-12 15:42:53.502 [API] [CON] Connection with: MNESlCI ended: undefined
dashboard_1  | 2018-09-12 15:42:54.136 [API] [CON] Connected host2
dashboard_1  | 2018-09-12 15:42:54.149 [API] [BLK] Block: 84 from: host2
dashboard_1  | 2018-09-12 15:42:54.160 [API] [STA] Stats from: host2
dashboard_1  | 2018-09-12 15:42:54.258 [API] [HIS] Got history from: host2
host3        | 2018-09-12 15:42:55 UTC    2/25 peers     90 KiB chain   17 KiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,    2 req/s,  125 µs
dashboard_1  | 2018-09-12 15:42:56.704 [API] [CON] Connection with: MNESl-I ended: undefined
dashboard_1  | 2018-09-12 15:42:57.398 [API] [CON] Connected host3
dashboard_1  | 2018-09-12 15:42:57.420 [API] [BLK] Block: 84 from: host3
dashboard_1  | 2018-09-12 15:42:57.428 [API] [STA] Stats from: host3
dashboard_1  | 2018-09-12 15:42:57.516 [API] [HIS] Got history from: host3
dashboard_1  | 2018-09-12 15:42:59.776 [API] [CON] Connection with: MNESmkO ended: undefined
dashboard_1  | 2018-09-12 15:43:00.460 [API] [CON] Connected host1
dashboard_1  | 2018-09-12 15:43:00.476 [API] [BLK] Block: 84 from: host1
dashboard_1  | 2018-09-12 15:43:00.481 [API] [STA] Stats from: host1
dashboard_1  | 2018-09-12 15:43:00.582 [API] [HIS] Got history from: host1
dashboard_1  | 2018-09-12 15:43:03.132 [API] [CON] Connection with: MNESnYk ended: undefined
dashboard_1  | 2018-09-12 15:43:03.781 [API] [CON] Connected host2
dashboard_1  | 2018-09-12 15:43:03.797 [API] [BLK] Block: 84 from: host2
dashboard_1  | 2018-09-12 15:43:03.802 [API] [STA] Stats from: host2
dashboard_1  | 2018-09-12 15:43:03.907 [API] [HIS] Got history from: host2
dashboard_1  | 2018-09-12 15:43:06.388 [API] [CON] Connection with: MNESoLi ended: undefined
dashboard_1  | 2018-09-12 15:43:07.019 [API] [CON] Connected host3
dashboard_1  | 2018-09-12 15:43:07.035 [API] [BLK] Block: 84 from: host3
dashboard_1  | 2018-09-12 15:43:07.041 [API] [STA] Stats from: host3
dashboard_1  | 2018-09-12 15:43:07.154 [API] [HIS] Got history from: host3
dashboard_1  | 2018-09-12 15:43:09.455 [API] [CON] Connection with: MNESp5a ended: undefined
dashboard_1  | 2018-09-12 15:43:10.068 [API] [CON] Connected host1
dashboard_1  | 2018-09-12 15:43:10.080 [API] [BLK] Block: 84 from: host1
dashboard_1  | 2018-09-12 15:43:10.085 [API] [STA] Stats from: host1
dashboard_1  | 2018-09-12 15:43:10.183 [API] [HIS] Got history from: host1
host2        | 2018-09-12 15:43:10 UTC    2/25 peers     90 KiB chain   17 KiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,    2 req/s,  131 µs
dashboard_1  | 2018-09-12 15:43:12.773 [API] [CON] Connection with: MNESpvP ended: undefined
dashboard_1  | 2018-09-12 15:43:13.394 [API] [CON] Connected host2
dashboard_1  | 2018-09-12 15:43:13.410 [API] [BLK] Block: 84 from: host2
dashboard_1  | 2018-09-12 15:43:13.417 [API] [STA] Stats from: host2
dashboard_1  | 2018-09-12 15:43:13.522 [API] [HIS] Got history from: host2
dashboard_1  | 2018-09-12 15:43:16.025 [API] [CON] Connection with: MNESqi3 ended: undefined
dashboard_1  | 2018-09-12 15:43:16.685 [API] [CON] Connected host3
dashboard_1  | 2018-09-12 15:43:16.702 [API] [BLK] Block: 84 from: host3
dashboard_1  | 2018-09-12 15:43:16.714 [API] [STA] Stats from: host3
dashboard_1  | 2018-09-12 15:43:16.810 [API] [HIS] Got history from: host3
dashboard_1  | 2018-09-12 15:43:19.066 [API] [CON] Connection with: MNESrRh ended: undefined
dashboard_1  | 2018-09-12 15:43:19.749 [API] [CON] Connected host1
dashboard_1  | 2018-09-12 15:43:19.765 [API] [BLK] Block: 84 from: host1
dashboard_1  | 2018-09-12 15:43:19.769 [API] [STA] Stats from: host1
dashboard_1  | 2018-09-12 15:43:19.890 [API] [HIS] Got history from: host1

Thanks in advance.

invalid type: string "all", expected a sequence for key `rpc.cors`

when i start parity with parity-deploy project, it shows me

Loading config file from /parity/authority.toml
You might have supplied invalid parameters in config file.
invalid type: string "all", expected a sequence for key `rpc.cors`

and, the commands i used ware

./parity-deploy.sh --config aura
docker-compose up

ERROR: Encountered errors while bringing up the project.

./parity-deploy.sh --config aura

threebody@deepin:~/Desktop/POA/parity-deploy$ docker-compose up -d
Starting 772123ad77a3_host1 ... error

ERROR: for 772123ad77a3_host1  Cannot start service host1: b'linux spec user: unable to find user parity: no matching entries in passwd file'

ERROR: for host1  Cannot start service host1: b'linux spec user: unable to find user parity: no matching entries in passwd file'
ERROR: Encountered errors while bringing up the project.

Parity install script failing for specific version

The Parity client install script fails when using a specific version. Example:
bash <(curl https://get.parity.io -Lk) -r v1.10.6

dpkg-deb: error: '/tmp/tmp.VAwOMY2BP7/parity_1.10.6_ubuntu_amd64.deb.md5' is not a debian format archive

The problem is that the installation script will accidentally download the .md5 file instead of the .deb file.
https://raw.githubusercontent.com/paritytech/scripts/master/get-parity.sh

This began failing when the versioned vanity-service began returning .md5 files.
https://vanity-service.parity.io/parity-binaries?architecture=x86_64&format=markdown&os=linux&version=stable

Simple fix in installation script is to filter out md5 files:
MD=$(curl -Ss ${LOOKUP_URL} | grep -v sha256 | grep deb | grep -v md5)

tendermint?

Cleaning up:

docker-compose down -v
sudo rm -rf data/ deployment/ docker-compose.yml

Is this the right way to create a tendermint network?

./parity-deploy.sh --config tendermint --name mytm --nodes 4 
read EC key
read EC key
read EC key
read EC key

but ^ results in this error:

docker-compose up
Creating network "paritytech_parity-deploy_default" with the default driver
Creating host4 ... done
Creating host2 ... done
Creating host3 ... done
Creating host1 ... done
Attaching to host4, host2, host3, host1
host4    | Loading config file from /parity/authority.toml
host3    | Loading config file from /parity/authority.toml
host4    | Spec json is invalid: missing field `gasLimitBoundDivisor` at line 23 column 5
host3    | Invalid node address format given for a boot node: enode://9e85e23f36630fc60ebdab335f5031a6ffe631f10524713f210e638ddc8ca681350f2983b845f285d8de7529d18ac09805182bcdcd91d80bf46798d9f114ae19@host2:30303
host2    | Loading config file from /parity/authority.toml
host2    | Spec json is invalid: missing field `gasLimitBoundDivisor` at line 23 column 5
host1    | Loading config file from /parity/authority.toml
host1    | Invalid node address format given for a boot node: enode://9e85e23f36630fc60ebdab335f5031a6ffe631f10524713f210e638ddc8ca681350f2983b845f285d8de7529d18ac09805182bcdcd91d80bf46798d9f114ae19@host2:30303
host3 exited with code 1
host2 exited with code 1
host4 exited with code 1
host1 exited with code 1

make config pieces JSON compliant / (FR) allow to change spec parameters

I cannot get past this:

jq '.genesis.gasLimit = "0x2625A00"' config/spec/genesis/aura

and I suppose that is because the file looks like this:

    "genesis": {
        "seal": {
            "authorityRound": {
                "step": "0x0",
                "signature": "0x0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
            }
        },
        "difficulty": "0x20000",
        "gasLimit": "0x1312D00"
    },

and not like this

{   "genesis": {
        "seal": {
            "authorityRound": {
                "step": "0x0",
                "signature": "0x0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
            }
        },
        "difficulty": "0x20000",
        "gasLimit": "0x1312D00"
    }}

Could you perhaps in a future version make the separate config pieces JSON compliant? Then parameters are easier to change:

jq '.genesis.gasLimit = "0x2625A00"' ~/tmp.txt 
{
  "genesis": {
    "seal": {
      "authorityRound": {
        "step": "0x0",
        "signature": "0x0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
      }
    },
    "difficulty": "0x20000",
    "gasLimit": "0x2625A00"
  }
}


And/or:

(How) can I change the genesis parameter on the commandline

DEPLOYARGS="--nodes 4 --config aura --name myaura"
NODEARGS="--geth --jsonrpc-server-threads 10 --tx-queue-size 20000 --cache-size 4096 --gas-floor-target 40000000 --tx-queue-mem-limit 0"
./parity-deploy.sh $DEPLOYARGS $NODEARGS 

perhaps like this?

SPEC='.genesis.gasLimit = "0x2625A00"'
./parity-deploy.sh $DEPLOYARGS --spec $SPEC $NODEARGS 

Test transaction corpora

Generate files with json arrays of the following RPC objects:

  • zero value tx from account to 0: eth, personal
  • presigned zero value tx from account to itself
  • presigned zero value tx from multiple accounts
  • realistic public net txs
  • contract deployments
  • skipped nonce

keygen script forces linux architecture

Should be a simple fix but the script to install ethkey in ./config/utils/keygen.sh, installs the linux binary only.

ETHKEY_URL=`curl -sS "https://vanity-service.parity.io/parity-binaries?version=stable&format=markdown&os=linux&architecture=x86_64"

Should have an option to specify the different architectures and os types on the server.

Can I use Parity UI for to connect to my private network?

Hi,

I've setup successfully my private network using the next command:

./parity-deploy.sh --config aura --nodes 3 --ethstats

Everything looks ok through Etherstats Dashboard using the URL http://localhost:3001

After that, I've installed Parity UI from here...

https://github.com/parity-js/shell

...and when I try to connect request me enter a token using the next command:

parity signer new-token

My questions are:

  • Can I use Parity UI for to connect to my private network?
  • Where I should execute the command? parity signer new-token

Thanks in advance!

Does not work at all on OSX

I was trying to generate a new docker config on OSX, but it does not work at all:

  • parity is installed by homebrew, but if [ ! -f /usr/bin/parity ] || [ ! "$PARITY_RELEASE" == "" ] ; then is not the correct check since it reisdes in /usr/local/bin/parity. The oneline installer tries to do something funky with the keychain and then fails.

  • sed on OSX is not gnu sed.

sed: 1: "config/spec/example.spec": command c expects \ followed by text
sed: 1: "config/spec/example.spec": command c expects \ followed by text
sed: 1: "docker-compose.yml": extra characters at the end of d command

yaml misformated

Latest commit: ./parity-deploy.sh --config aura -n 5
docker-compose up -d

ERROR: yaml.parser.ParserError: while parsing a block mapping
  in "./docker-compose.yml", line 4, column 8
expected <block end>, but found '-'
  in "./docker-compose.yml", line 5, column 8

instantseal password empty & chainname ignored

thorough cleaning:

docker-compose down -v
docker rm $(docker ps -a -q); docker rmi $(docker images -q)
sudo rm -rf data/ deployment/ docker-compose.yml
sudo ./clean.sh 

there is a password created:

./parity-deploy.sh --config dev --name instantseal
cat  deployment/is_authority/password 

results in

s4LKh0oCw4jH1g1n

but then something's wrong:

docker-compose up

./deploy.py 
...
Traceback (most recent call last):
  File "./deploy.py", line 136, in <module>
    deployTheContract(contract_source_file=CONTRACT_SOURCE)
  File "./deploy.py", line 105, in deployTheContract
    print ("unlock: ", unlockAccount())
  File "/home/akrueger/Documents/Code/gitlab/electronDLT/chainhammer/clienttools.py", line 94, in unlockAccount
    duration=duration)
  File "/home/akrueger/Documents/Code/envs/py3eth/lib/python3.5/site-packages/web3/personal.py", line 43, in unlockAccount
    [account, passphrase, duration],
  File "/home/akrueger/Documents/Code/envs/py3eth/lib/python3.5/site-packages/web3/manager.py", line 110, in request_blocking
    raise ValueError(response["error"])

ValueError: {'code': -32023, 'data': 'InvalidPassword', 'message': 'Unable to unlock the account.'}

found it out like this

geth attach http://localhost:8545
Welcome to the Geth JavaScript console!

instance: Parity//v1.11.10-stable-31720e6-20180830/x86_64-linux-gnu/rustc1.28.0
coinbase: 0x00a329c0648769a73afac7f9381e08fb43dbea72
at block: 0 (Thu, 01 Jan 1970 01:00:00 BST)
 modules: eth:1.0 net:1.0 parity:1.0 parity_accounts:1.0 parity_set:1.0 personal:1.0 rpc:1.0 signer:1.0 traces:1.0 web3:1.0

> personal.unlockAccount(eth.accounts[0])
Unlock account 0x00a329c0648769a73afac7f9381e08fb43dbea72
Passphrase: 
true

instead of "s4LKh0oCw4jH1g1n", the password is ""

Client fails to setup due to race during docker node startup

When deploy is invoked with like ./parity-deploy.sh --config aura -n 1 -r nightly --min-gas-price 0 --enable-client --reserved-only, client node is created.

Unfortunately the following scenario is possible: https://gist.github.com/0x7CFE/df64afad8244e74156a772a6b2df28f0

tl;dr: Client fails to start due to failed name resolution (related to openethereum/parity-ethereum#6907). Looks like this happens because of a race between nodes. If host1 starts before client all is working as expected. However, client may try to resolve host1 before latter obtains an IP address.

In order to fix that, we need either fix the order in which nodes start or assign static addresses to nodes.

Client node is not added to the `reserved_peers` list

When client node is created using --enable-client looks like it is not added to the reserved_peers list. If --reserved-only option is passed it results in nodes not seeing each other.

I don't quite understand why client node is not set as reserved. Is there some reasoning for it?

small improvement: compare parity versions before downloading binary

reproduce like this:

PARITY_VERSION=v2.2.3
sudo rm -rf paritytech_parity-deploy
git clone https://github.com/paritytech/parity-deploy.git paritytech_parity-deploy
cd paritytech_parity-deploy
git checkout 1a6afd17ac75bdf6c9e9fefa1d3af13748dd9cfa
sudo ./clean.sh
./parity-deploy.sh -r $PARITY_VERSION --config aura --nodes 4 --geth
sed -i 's/parity:stable/parity:'$PARITY_VERSION'/g' docker-compose.yml
docker-compose up

results in:

Custom parity build set: v2.2.3
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3856  100  3856    0     0    759      0  0:00:05  0:00:05 --:--:--   996
Release selected is: v2.2.3
Parity 2.2.3 already installed

--> suggestion: Do not download if version is already wanted version. Then it would look like this:

Custom parity build set: v2.2.3
Parity 2.2.3 already installed, no download needed.

How to access the built-in account

The readme states:

Once you are logged into the web interface if you go to Add Accounts, then select the option recovery phrase and enter the account recovery phrase as password
You now have an account with lots of ether to send around.

But there is UI. Port 8180 is exposed:

CONTAINER ID        IMAGE                  COMMAND                  CREATED             STATUS              PORTS                                                                                                                                            NAMES
a3531f5cf832        parity/parity:stable   "./entrypoint.sh --f…"   30 seconds ago      Up 30 seconds       5001/tcp, 0.0.0.0:8080->8080/tcp, 0.0.0.0:8180->8180/tcp, 0.0.0.0:8545-8546->8545-8546/tcp, 8082-8083/tcp, 0.0.0.0:30303->30303/tcp, 30303/udp   host1

But:

$ curl localhost:8180
curl: (56) Recv failure: Connection reset by peer

Isn't UI moved to Parity UI? The documentation may need to be updated or expanded.

With UI or not, my question is how do I unlock the built-in account 0x00Ea169ce7e0992960D3BdE6F5D539C955316432 ?

I could not locate its private key or password anywhere.

This is related to #86

I use parity-deploy with a command:

$ ./parity-deploy.sh --name somename --config aura --nodes 1

Ethstats

./parity-deploy.sh --config aura --ethstats, go to 3001 and no nodes appear

Download only once

Especially ethstats takes pretty long to get for multiple nodes, though then setup is more single machine specific.

ethkey not found

Hi there,

I got the next error...

./config/utils/keygen.sh: 5: ./config/utils/keygen.sh: ethkey: not found

...when I execute the next command:

./parity-deploy.sh --config aura --nodes 3 --ethstats

I fulfill all the requirements:

  1. OpenSSL 1.0.2g 1 Mar 2016
  2. pip 18.0
  3. Docker version 18.06.1-ce, build e68fc7a
  4. docker-compose version 1.22.0, build f46880fe

I'm using Ubunt 16.04

Thank you.

(FR) give account balance to default account

The default account has no money:

geth attach http://localhost:8545

Welcome to the Geth JavaScript console!
instance: Parity//v1.11.11-stable-cb03f38-20180910/x86_64-linux-gnu/rustc1.28.0
coinbase: 0x9cfd59da9b75f06719de2c8ccead40e8e3799bfc
at block: 16 (Mon, 03 Dec 2018 18:28:15 GMT)
 modules: eth:1.0 net:1.0 parity:1.0 parity_accounts:1.0 parity_set:1.0 personal:1.0 rpc:1.0 signer:1.0 traces:1.0 web3:1.0

> eth.accounts
["0x9cfd59da9b75f06719de2c8ccead40e8e3799bfc"]

> eth.getBalance(eth.accounts[0])
0

I see that via spec.json you have given money to one account:

> eth.getBalance("0x00Ea169ce7e0992960D3BdE6F5D539C955316432")
1.606938044258990275541962092341162602522202993782792835301376e+60

it is just not available on the http://localhost:8545 default node address.

Could you make your script give some money to that account?


P.S.: I started like this

cd paritytech_parity-deploy
git checkout a76a2f1b7173ff5d138e0cb66efdb939bfe33aab 
sudo ./clean.sh
./parity-deploy.sh --nodes 4 --config aura --name myaura --geth
sed -i 's/parity:stable/parity:v1.11.11/g' docker-compose.yml
docker-compose up

deployment/chain/spec.json: Is a directory

commit 6947f2b

ARGS="--db-compaction ssd --tracing off --gasprice 1000 --gas-floor-target 100000000000 --pruning fast --tx-queue-size 32768 --tx-queue-mem-limit 0 --no-warp --jsonrpc-threads 8 --no-hardware-wallets --no-dapps --no-secretstore-http --cache-size 4096 --scale-verifiers --num-verifiers 16"

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

results in:

./parity-deploy.sh: line 341: deployment/chain/spec.json: Is a directory

what helped was:

cd ..
sudo rm paritytech_parity-deploy -rf 
git clone https://github.com/paritytech/parity-deploy.git paritytech_parity-deploy
cd paritytech_parity-deploy
sudo ./clean.sh

then

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

came back without an error

Error: NO custom parity build set, downloading stable

Hi,

I got the following error after running ./parity-deploy.sh --config dev command:

$ ./parity-deploy.sh --config dev

NO custom parity build set, downloading stable
Warning: Invalid character is found in given range. A specified range MUST
Warning: have only digits in 'start'-'stop'. The server's response to this
Warning: request is uncertain.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (35) SSL peer handshake failed, the server most likely requires a client certificate to connect
grep: /etc/*-release: No such file or directory
using instantseal
Fatal: Failed to read passphrase: liner: function not supported in this terminal
mktemp: illegal option -- p
usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
       mktemp [-d] [-q] [-u] -t prefix
./parity-deploy.sh: line 59: $SPEC_FILE: ambiguous redirect
./parity-deploy.sh: line 60: parity: command not found
usage: rm [-f | -i] [-dPRrvW] file ...
       unlink file
sed: 1: "docker-compose.yml": extra characters at the end of d command

How do I fix this?

Thanks.

No UI

./parity-deploy.sh --config aura (or --release nightly), nothing on 8180

Error upgrading parity data: CannotCreateConfigPath

Here's what I did:

 ./parity-deploy.sh --config aura
docker-compose up

Here's what I see:

Attaching to host1
host1    | Loading config file from /parity/authority.toml
host1    | Error upgrading parity data: CannotCreateConfigPath
host1 exited with code 1

I'm running everything as root user on a VM.

unable to find user parity: no matching entries in passwd file

found a new one:

git clone https://github.com/paritytech/parity-deploy.git paritytech_parity-deploy
cd paritytech_parity-deploy/
git log | head -n 5
commit 11b64e11cc9403101aa1e0db0bfbc72997e01a74
Merge: 80a0fd8 c1dc457
Author: ddorgan <[email protected]>
Date:   Wed Dec 12 21:29:02 2018 +0000
which parity
sudo rm /usr/bin/parity
./parity-deploy.sh -r v1.11.11 --nodes 4 --config aura --name myaura --geth --gasprice 0 --tx-queue-mem-limit 0
sed -i 's/parity:stable/parity:v1.11.11/g' docker-compose.yml
jq ".engine.authorityRound.params.stepDuration = 5" deployment/chain/spec.json > tmp; mv tmp deployment/chain/spec.json
docker-compose up
ERROR: for host4  Cannot start service host4: b'linux spec user: unable to find user parity: no matching entries in passwd file'
...

Error upgrading parity data: CannotCreateConfigPath

git clone https://github.com/paritytech/parity-deploy.git paritytech_parity-deploy
cd paritytech_parity-deploy
./parity-deploy.sh --config dev --name instantseal --geth
docker-compose up

results in

Pulling host1 (parity/parity:stable)...
stable: Pulling from parity/parity
3b37166ec614: Pull complete
504facff238f: Pull complete
ebbcacd28e10: Pull complete
c7fb3351ecad: Pull complete
2e3debadcbf7: Pull complete
7f6af3eb31f4: Pull complete
f3f7881c4019: Pull complete
50d35ce58406: Pull complete
9a3b96a0f918: Pull complete
1fe9fb6fb58c: Pull complete
c83743d94dd0: Pull complete
969cd73ce977: Pull complete
c74e70272632: Pull complete
Digest: sha256:20eccf6b6d28fa0e5f14b6b5dd3b63625e17e8114e098b40dceec2bf5ee154e4
Status: Downloaded newer image for parity/parity:stable
Creating host1 ... done
Attaching to host1
host1    | Loading config file from /parity/authority.toml
host1    | Error upgrading parity data: CannotCreateConfigPath
host1 exited with code 1

(FR) user defined parameters

At the moment I am manually adding

--geth --jsonrpc-server-threads 100 --tx-queue-size 20000 --cache-size 4096 --tracing off --gas-floor-target 50000000 --pruning fast --tx-queue-mem-limit 0 --no-dapps --no-secretstore-http

to the resulting docker-compose.yml after running ./parity-deploy.sh --config aura --name myaura --nodes 4

A new CLI switch could be useful, like

NODEARGS="--geth --jsonrpc-server-threads 100 --tx-queue-size 20000 --cache-size 4096 --tracing off --gas-floor-target 50000000 --pruning fast --tx-queue-mem-limit 0 --no-dapps --no-secretstore-http"
./parity-deploy.sh --config aura --name myaura --nodes 4 --args $NODEARGS
docker-compose up

Invalid node address format given for a boot node

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

using instantseal
read EC key
docker-compose up

Starting host1 ... done
Attaching to host1
host1    | Loading config file from /parity/authority.toml
host1    | Invalid node address format given for a boot node: enode://0c4a30a3ec29b3d7458b2f45b331f16b9a6c17ec2c3f6cd45114b13e08b66631ef38a12f0d814cef778ecbfba89d540c81645811894c3f34358b0336c37d3ecb@host2:30303
host1 exited with code 1

ethkey: error while loading shared libraries: libboost_filesystem.so.1.55.0: cannot open shared object file: No such file or directory

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

today results in

ethkey: error while loading shared libraries: libboost_filesystem.so.1.55.0: cannot open shared object file: No such file or directory
ethkey: error while loading shared libraries: libboost_filesystem.so.1.55.0: cannot open shared object file: No such file or directory
ethkey: error while loading shared libraries: libboost_filesystem.so.1.55.0: cannot open shared object file: No such file or directory
ethkey: error while loading shared libraries: libboost_filesystem.so.1.55.0: cannot open shared object file: No such file or directory

System is up-to-date Debian stretch.

Examples are broken

Tried this:

> ./parity-deploy.sh --config dev
> docker-compose up

Saw this:

Starting host1 ... done
Attaching to host1
host1    | Loading config file from /parity/authority.toml
host1    | Invalid node address format given for a boot node: enode://@host1:30303
host1 exited with code 1

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

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 5726733

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 [email protected]
dashboard_1  | npm info using [email protected]
dashboard_1  | npm info lifecycle [email protected]~prestart: [email protected]
dashboard_1  | npm info lifecycle [email protected]~start: [email protected]
dashboard_1  | 
dashboard_1  | > [email protected] 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 [email protected]. 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

Question about key.priv and address.txt

Just two quick questions about key.priv and address.txt.

Why the address I generate from private key which is stored in key.priv is different from the address that is stored in address.txt?

What if I want to use my own account as miner in aura?

(FR) fix a certain version

this morning, using parity-deploy resulted in

Parity/v1.11.11-stable-cb03f38-20180910/x86_64-linux-gnu/rustc1.28.0

now today after lunch, suddenly that switched to

Parity-Ethereum/v2.0.4-beta-e2e1d22-20180910/x86_64-linux-gnu/rustc1.28.0

not good:

  • stuff just changes which then breaks other stuff.
  • suddenly stable is switched for beta (sic!)
  • results of e.g. benchmarking are not replicable anymore.

--> Feature Request: Allow parity-deploy.sh to fix one specific parity version.

Running docker-compose logs returns no token

Currently trying to utilize this parity repo with a PoA chain and I can't seem to get an appropriate account that is funded. I am trying to open the UI with SSH'ed into a remote node. I have tried the | grep token option, but it returns nothing from the logs. When I go to inspect the logs manually, I don't see any token generated:

host2 | Loading config file from /parity/authority.toml
host2 | 2018-08-16 13:21:18 UTC Starting Parity-Ethereum/v2.0.1-beta-e7dc0be-20180726/x86_64-linux-gnu/rustc1.27.2
host2 | 2018-08-16 13:21:18 UTC Keys path /parity/data/keys/MPDL
host2 | 2018-08-16 13:21:18 UTC DB path /parity/data/chains/MPDL/db/0796728f28a12423
host2 | 2018-08-16 13:21:18 UTC State DB configuration: fast
host2 | 2018-08-16 13:21:18 UTC Operating mode: active
host2 | 2018-08-16 13:21:18 UTC Configured for MPDL using AuthorityRound engine
host2 | 2018-08-16 13:21:23 UTC Public node URL: enode://49accab3db8be0bae061f3e160420b15e6b0509b44fa287bcf5d18f4f6c5a9c3c960edd31561af4747b88cdb6d491f4a40ddb84b55bfa44b29dbc5c38ed64c39@172.18.0.4:30303
host2 | 2018-08-16 13:21:53 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host2 | 2018-08-16 13:22:23 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host2 | 2018-08-16 13:22:53 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host3 | Loading config file from /parity/authority.toml
host3 | 2018-08-16 13:21:18 UTC Starting Parity-Ethereum/v2.0.1-beta-e7dc0be-20180726/x86_64-linux-gnu/rustc1.27.2
host3 | 2018-08-16 13:21:18 UTC Keys path /parity/data/keys/MPDL
host3 | 2018-08-16 13:21:18 UTC DB path /parity/data/chains/MPDL/db/0796728f28a12423
host3 | 2018-08-16 13:21:18 UTC State DB configuration: fast
host3 | 2018-08-16 13:21:18 UTC Operating mode: active
host3 | 2018-08-16 13:21:18 UTC Configured for MPDL using AuthorityRound engine
host3 | 2018-08-16 13:21:23 UTC Public node URL: enode://57e3319313cd966a95e5a3f73b7f4954f88693ac36b7e4a46525dde705fe7aaa5be2e6736d60190e3289591f0c68916c887d675d2acb4ac10e8f500aea26b9f6@172.18.0.3:30303
host3 | 2018-08-16 13:21:53 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host3 | 2018-08-16 13:22:23 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host3 | 2018-08-16 13:22:53 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host1 | Loading config file from /parity/authority.toml
host1 | 2018-08-16 13:21:19 UTC Starting Parity-Ethereum/v2.0.1-beta-e7dc0be-20180726/x86_64-linux-gnu/rustc1.27.2
host1 | 2018-08-16 13:21:19 UTC Keys path /parity/data/keys/MPDL
host1 | 2018-08-16 13:21:19 UTC DB path /parity/data/chains/MPDL/db/0796728f28a12423
host1 | 2018-08-16 13:21:19 UTC State DB configuration: fast
host1 | 2018-08-16 13:21:19 UTC Operating mode: active
host1 | 2018-08-16 13:21:19 UTC Configured for MPDL using AuthorityRound engine
host1 | 2018-08-16 13:21:24 UTC Public node URL: enode://70f471330433ff3ab8d9461e00899d1be6b11c4c178f627d90d5a4b836e9fdbd27f1ab66a5bec5b335c189fabeeca819acf9baeff303af70b2a48b814ce2000d@172.18.0.2:30303
host1 | 2018-08-16 13:21:49 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host1 | 2018-08-16 13:22:19 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host1 | 2018-08-16 13:22:49 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
lawton@vm65:~/parity-deploy$ docker-compose logs -f
Attaching to host2, host3, host1
host2 | Loading config file from /parity/authority.toml
host2 | 2018-08-16 13:21:18 UTC Starting Parity-Ethereum/v2.0.1-beta-e7dc0be-20180726/x86_64-linux-gnu/rustc1.27.2
host2 | 2018-08-16 13:21:18 UTC Keys path /parity/data/keys/MPDL
host2 | 2018-08-16 13:21:18 UTC DB path /parity/data/chains/MPDL/db/0796728f28a12423
host2 | 2018-08-16 13:21:18 UTC State DB configuration: fast
host2 | 2018-08-16 13:21:18 UTC Operating mode: active
host2 | 2018-08-16 13:21:18 UTC Configured for MPDL using AuthorityRound engine
host2 | 2018-08-16 13:21:23 UTC Public node URL: enode://49accab3db8be0bae061f3e160420b15e6b0509b44fa287bcf5d18f4f6c5a9c3c960edd31561af4747b88cdb6d491f4a40ddb84b55bfa44b29dbc5c38ed64c39@172.18.0.4:30303
host2 | 2018-08-16 13:21:53 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host2 | 2018-08-16 13:22:23 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host2 | 2018-08-16 13:22:53 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host2 | 2018-08-16 13:23:20 UTC Imported #1 0xc51d…948a (0 txs, 0.00 Mgas, 0 ms, 0.57 KiB)
host3 | Loading config file from /parity/authority.toml
host3 | 2018-08-16 13:21:18 UTC Starting Parity-Ethereum/v2.0.1-beta-e7dc0be-20180726/x86_64-linux-gnu/rustc1.27.2
host3 | 2018-08-16 13:21:18 UTC Keys path /parity/data/keys/MPDL
host3 | 2018-08-16 13:21:18 UTC DB path /parity/data/chains/MPDL/db/0796728f28a12423
host3 | 2018-08-16 13:21:18 UTC State DB configuration: fast
host3 | 2018-08-16 13:21:18 UTC Operating mode: active
host3 | 2018-08-16 13:21:18 UTC Configured for MPDL using AuthorityRound engine
host3 | 2018-08-16 13:21:23 UTC Public node URL: enode://57e3319313cd966a95e5a3f73b7f4954f88693ac36b7e4a46525dde705fe7aaa5be2e6736d60190e3289591f0c68916c887d675d2acb4ac10e8f500aea26b9f6@172.18.0.3:30303
host3 | 2018-08-16 13:21:53 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host3 | 2018-08-16 13:22:23 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host3 | 2018-08-16 13:22:53 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host1 | Loading config file from /parity/authority.toml
host1 | 2018-08-16 13:21:19 UTC Starting Parity-Ethereum/v2.0.1-beta-e7dc0be-20180726/x86_64-linux-gnu/rustc1.27.2
host1 | 2018-08-16 13:21:19 UTC Keys path /parity/data/keys/MPDL
host1 | 2018-08-16 13:21:19 UTC DB path /parity/data/chains/MPDL/db/0796728f28a12423
host1 | 2018-08-16 13:21:19 UTC State DB configuration: fast
host1 | 2018-08-16 13:21:19 UTC Operating mode: active
host1 | 2018-08-16 13:21:19 UTC Configured for MPDL using AuthorityRound engine
host1 | 2018-08-16 13:21:24 UTC Public node URL: enode://70f471330433ff3ab8d9461e00899d1be6b11c4c178f627d90d5a4b836e9fdbd27f1ab66a5bec5b335c189fabeeca819acf9baeff303af70b2a48b814ce2000d@172.18.0.2:30303
host1 | 2018-08-16 13:21:49 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host1 | 2018-08-16 13:22:19 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host1 | 2018-08-16 13:22:49 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host1 | 2018-08-16 13:23:19 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host3 | 2018-08-16 13:23:23 UTC 0/25 peers 9 KiB chain 7 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host2 | 2018-08-16 13:23:23 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host1 | 2018-08-16 13:23:24 UTC Imported #1 0x9438…7f20 (0 txs, 0.00 Mgas, 0 ms, 0.57 KiB)
host3 | 2018-08-16 13:23:28 UTC Imported #1 0x7f34…739d (0 txs, 0.00 Mgas, 0 ms, 0.57 KiB)
host1 | 2018-08-16 13:23:49 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host3 | 2018-08-16 13:23:53 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host2 | 2018-08-16 13:23:53 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host1 | 2018-08-16 13:24:19 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host3 | 2018-08-16 13:24:23 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host2 | 2018-08-16 13:24:23 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host1 | 2018-08-16 13:24:49 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host3 | 2018-08-16 13:24:53 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host2 | 2018-08-16 13:24:53 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host1 | 2018-08-16 13:25:19 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host2 | 2018-08-16 13:25:20 UTC Imported #2 0xe996…a121 (0 txs, 0.00 Mgas, 2 ms, 0.57 KiB)
host3 | 2018-08-16 13:25:23 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host2 | 2018-08-16 13:25:23 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host1 | 2018-08-16 13:25:24 UTC Imported #2 0x6d46…12aa (0 txs, 0.00 Mgas, 0 ms, 0.57 KiB)
host3 | 2018-08-16 13:25:28 UTC Imported #2 0x8405…c039 (0 txs, 0.00 Mgas, 0 ms, 0.57 KiB)
host1 | 2018-08-16 13:25:49 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 67 µs
host3 | 2018-08-16 13:25:53 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host2 | 2018-08-16 13:25:53 UTC 0/25 peers 9 KiB chain 8 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
host1 | 2018-08-16 13:26:05 UTC Blocked connection from parity://1.ui.parity using invalid token.
host1 | 2018-08-16 13:26:05 UTC Blocked connection to WebSockets server from untrusted origin: Some("parity://1.ui.parity")
host1 | 2018-08-16 13:26:05 UTC Blocked connection to WebSockets server from untrusted origin: Some("parity://1.ui.parity")
host1 | 2018-08-16 13:26:05 UTC Blocked connection from parity://1.ui.parity using invalid token.
host1 | 2018-08-16 13:26:05 UTC Blocked connection to WebSockets server from untrusted origin: Some("parity://1.ui.parity")
host1 | 2018-08-16 13:26:05 UTC Blocked connection from parity://1.ui.parity using invalid token.
host1 | 2018-08-16 13:26:05 UTC Blocked connection to WebSockets server from untrusted origin: Some("parity://1.ui.parity")
host1 | 2018-08-16 13:26:05 UTC Blocked connection to WebSockets server from untrusted origin: Some("parity://1.ui.parity")

The only hint is currently the UTC Blocked connection using invalid token. When I use the command to generate a new token, I receive the error:

Error generating token: Os { code: 2, kind: NotFound, message: "No such file or directory" }

Please let me know if you need additional info.

(v2.2.3) Spec json is invalid: unknown field `gasLimitBoundDivisor`

@5chdn asked to try version v2.2.3:

does this happen with 2.2.3?

but besides #85 it looks as if v2 needs a different spec.json ?

reproduce this

git clone https://github.com/paritytech/parity-deploy paritytech_parity-deploy
cd paritytech_parity-deploy
git log | head -n 5

commit 0e0624814f21e9fe05a77b2168fa257f915bbb3d
Merge: 359c3c2 eaf31d4
...
Date:   Thu Nov 1 15:27:06 2018 +0100
sudo ./clean.sh
./parity-deploy.sh -r v2.2.3 --config dev --geth

Custom parity build set: v2.2.3
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3856  100  3856    0     0   6072      0 --:--:-- --:--:-- --:--:--  6072
Release selected is: v2.2.3
Parity 2.2.3 already installed

using instantseal

Invalid argument: generate

Spec json is invalid: unknown field `gasLimitBoundDivisor`, 
expected one of `stepDuration`, `validators`, `startStep`, `validateScoreTransition`, `validateStepTransition`, `immediateTransitions`, `blockReward`, `blockRewardContractTransition`, `blockRewardContractAddress`, `blockRewardContractCode`, `maximumUncleCountTransition`, `maximumUncleCount`, `emptyStepsTransition`, `maximumEmptySteps` at line 6 column 39

Invalid argument: generate

Situation:

cd paritytech_parity-deploy
git pull
Already up-to-date.
git checkout master
Already on 'master'
Your branch is up-to-date with 'origin/master'.
git log
commit 0e0624814f21e9fe05a77b2168fa257f915bbb3d
Date:   Thu Nov 1 15:27:06 2018 +0100

Problem:

./parity-deploy.sh --config dev -r v1.11.11
Custom parity build set: v1.11.11
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3856  100  3856    0     0   5851      0 --:--:-- --:--:-- --:--:--  5851
Release selected is: v1.11.11
Parity 1.11.11 already installed
using instantseal

Invalid argument: generate

no problem:

git checkout 2a91e3ae0d4a92053296d98d2f0d765dea539172
HEAD is now at 2a91e3a... Fix section of gasLimitBoundDivisor for tendermint.
git log
...
Date:   Tue Sep 4 14:30:45 2018 +0200

./parity-deploy.sh --config dev -r v1.11.11
Custom parity build set: v1.11.11
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3856  100  3856    0     0  14592      0 --:--:-- --:--:-- --:--:-- 14606
Release selected is: v1.11.11
Parity 1.11.11 already installed
using instantseal
read EC key

local parity:

parity --version
Parity
  version Parity/v1.11.11-stable-cb03f380a-20180910/x86_64-linux-gnu/rustc1.28.0

after execute parity-deploy.sh - i got the result "read EC key"

if i execute the "sudo ./parity-deploy.sh --config aura --nodes 2 --ethstats" i got the result "read EC key". I have no Idea what is wrong. i have no UI on http://localhost:8180/.

i use the ubuntu:

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 17.10
Release: 17.10
Codename: artful

my history:

1 ping google.com
2 g++ --version
3 sudo apt-get install g++
4 g++ --version
5 ls
6 cd ..
7 ls
8 cd mnt/
9 ls
10 cd ..
11 cd /home/osboxes/Downloads
12 ls
13 cd vmware-tools-distrib/
14 ls
15 sudo ./vmware-install.pl
16 cd /home/osboxes/Downloads
17 ls
18 cd vmware-tools-distrib/
19 ls
20 sudo ./vmware-install.pl
21 g++ --version
22 sudo apt-get install build-essentail autoconf automake libtool pkg-config git
23 sudo apt-get install libboost-all-dev
24 wget https://raw.githubusercontent.com/libbitcoin/version3/install.sh
25 sudo
26 su
27 wget https://raw.githubusercontent.com/libbitcoin/version3/install.sh
28 wget https://raw.githubusercontent.com/libbitcoin/libbitcoin/version3/install.sh
29 chmod +x install.sh
30 ls
31 ./install.sh
32 su
33 sudo
34 pwd
35 cd /
36 ls
37 cd home/
38 ls
39 cd osboxes/
40 ls
41 ./install.sh
42 sudo ./install.sh
43 sudo apt-get install git
44 sudo ./install.sh
45 ls
46 dir
47 cd build-libbitcoin/
48 ls
49 cd /
50 ls
51 cd usr/
52 ls
53 cd local/
54 ls
55 cd bin/
56 l
57 ls
58 cd ..
59 ls
60 cd /
61 ls
62 cd lib
63 ls
64 cd /
65 cd lib64
66 ls
67 cd ..
68 ls
69 pwd
70 cd home/
71 ls
72 cd osboxes/
73 ls
74 ./install.sh --with-icu
75 sudo ./install.sh --with-icu
76 sudo ./install.sh --with-icu --with-qrencode --build-zlib --build-png --build-qrencode --build-boost --prefix=/home/osboxes/myprefix
77 sudo apt-get install make
78 sudo ./install.sh --with-icu --with-qrencode --build-zlib --build-png --build-qrencode --build-boost --prefix=/home/osboxes/myprefix
79 sudo ./install.sh CFLAGS="-Og -g" --prefix=/home/osboxes/myprefix
80 ls
81 cd build-libbitcoin/
82 ls
83 cd secp256k1/
84 ls
85 cd builds/
86 ls
87 cd msvc/
88 ls
89 cd build/
90 ls
91 ./buildall.bat
92 sudo ./buildall.bat
93 sudo apt-get install automake
94 sudo ./install.sh --with-icu --with-qrencode --build-zlib --build-png --build-qrencode --build-boost --prefix=/home/osboxes/myprefix
95 cd /home/
96 ls
97 cd osboxes/
98 ls
99 sudo ./install.sh --with-icu --with-qrencode --build-zlib --build-png --build-qrencode --build-boost --prefix=/home/osboxes/myprefix
100 bitcoin
101 bitcoin-cli
102 bx
103 bx seed
104 ec-add
105 ./autogen.sh
106 make
107 sudo apt-get install build-essential autoconf automake libtool pkg-config git
108 sudo apt-get install libboost-all-dev
109 wget https://raw.githubusercontent.com/libbitcoin/libbitcoin-explorer/version3/install.sh
110 chmod +x install.sh
111 sudo ./install.sh
112 help
113 seed
114 send-tx
115 cd /home/osboxes/build-libbitcoin/libbitcoin
116 ls
117 cd libtool
118 libtool
119 ls
120 cd configure
121 ls
122 ./libtool
123 ./libtool help
124 cd examples/
125 ls
126 cd libbitcoin_examples
127 ./libbitcoin_examples
128 bx
129 cd /usr/local/bin/
130 ls
131 sudo update-alternatives --install /usr/bin/g++
132 sudo apt-get install build-essential autoconf automake libtool pkg-config git
133 sudo apt-get install libboost-all-dev
134 /home/osboxes/build-libbitcoin/libbitcoin
135 cd /home/osboxes/Downloads
136 ls
137 bx-linux-x64-qrcode
138 vim bx-linux-x64-qrcode
139 notepad
140 edit
141 editor
142 sudo apt-get update
143 sudo apt-get upgrade
144 node -v
145 sudo apt-get install node
146 curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
147 sudo apt-get install curl
148 curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
149 sudo apt-get install -y nodejs
150 sudo apt-get install -y build-essential
151 node -v
152 sudo apt-get install git
153 git
154 npm
155 mkdir inbox
156 cd inbox/
157 npm init
158 ls
159 sudo apt-get install atom
160 atom
161 snap
162 snap install atom
163 snap install atom --classic
164 atom
165 ls
166 atom package.json
167 sudo apt-get install sublime-text-installer
168 sudo apt-get install atom
169 atom
170 sudo apt-get install vim
171 pwd
172 ls
173 cd inbox/
174 ls
175 cd..
176 ls
177 cd ..
178 ls
179 cd Desktop
180 ls
181 cd workspace/
182 ls
183 pwd
184 ls
185 cd ..
186 ls
187 cd workspace/
188 ls
189 cd inbox/
190 ls
191 noe compile.js
192 node compile.js
193 x node
194 ls
195 cd contracts/
196 ls
197 cd ..
198 ls
199 node
200 node -v
201 node compile.js
202 apt-get install solc
203 npm install -g solc
204 sudo npm install -g solc
205 node compile.js
206 npm install solc
207 sudo npm install solc
208 node compile.js
209 npm init
210 ls
211 node compile.js
212 edit compile.js
213 gedit compile.js
214 cd ..
215 npm init
216 node compile.js
217 node inbox/compile.js
218 gpedit inbox/contracts/inbox.sol
219 cd inbox/
220 cd contracts/
221 ls
222 gpedit inbox.sol
223 gedit inbox.sol
224 node inbox/compile.js
225 cd ..
226 ls
227 node compile.js
228 ls
229 cd test/
230 ls
231 mkdir test.js
232 ls
233 rm test.js/
234 su
235 rm test.js/
236 ls
237 gedit test.js
238 ls
239 gedit test.js
240 cd ..
241 npm run test
242 ls
243 cd test/
244 npm run test
245 npm Inbox.test.js
246 npm run Inbox.test.js
247 cd ..
248 npm run test
249 npm install remixd -g
250 sudo npm install remixd -g
251 npm i -g npm
252 sudo npm i -g npm
253 sudo apt-get update
254 sudo apt-get install openssl
255 sudo apt-get install bower
256 sudo npm install bower -g
257 sudo apt-get update && sudo apt-get -y upgrade
258 sudo apt-get install python3-pip
259 sudo pip install docker-compose --force --upgrade
260 pip install -U pip
261 sudo apt-get install pip
262 sudo apt-get install python-pip
263 sudo apt-get install python3-pip
264 pip install -U pip
265 sudo pip install docker-compose --force --upgrade
266 sudo apt-get update && sudo apt-get -y upgrade
267 sudo apt-get install docker
268 sudo chown -R osboxes .cache/ -v
269 sudo chown -R osboxes ./
270 pwd
271 ls
272 cd test/
273 sudo ./go.sh
274 npm i -g npm
275 sudo npm i -g npm
276 geth
277 ls
278 cd pari/
279 ls
280 cd parity-deploy/
281 ls
282 cat /monitor/app.json
283 cd monitor/
284 ls
285 cat app.json
286 cat config/spec/authority_round.toml
287 cd ..
288 ls
289 cat config/spec/authority_round.toml
290 sudo ./parity-deploy.sh --config aura --nodes 2 --ethstats
291 sudo docker-compose up
292 sudo ./parity-deploy.sh --config aura --nodes 2 --ethstats
293 sudo ./parity-deploy.sh --config aura --nodes 2 --ethstats -v
294 sudo ./parity-deploy.sh --config aura --nodes 2
295 sudo ./parity-deploy.sh
296 sudo apt-get -y install docker.io
297 sudo apt autoremove
298 openssl rand -base64 12
299 sudo openssl rand -base64 12
300 sudo ./parity-deploy.sh --config aura --nodes 2 --release
301 sudo ./parity-deploy.sh --config aura --nodes 2 --ethstats
302 install ntpdate
303 sudo apt-get install ntpdate
304 sudo ntpdate -s us.pool.ntp.org
305 ./parity-deploy.sh --config aura
306 genpw
307 sudo apt-get install -y pwgen
308 genpw
309 pwgen
310 ./parity-deploy.sh --config aura
311 sudo ./parity-deploy.sh --config aura
312 sudo curl -o parity-download.sh https://get.parity.io -Lk
313 parity-download.sh -r
314 ls
315 sudo ./parity-download.sh -r
316 sudo ./parity-deploy.sh --config aura
317 parity
318 sudo ./parity-deploy.sh --config aura
319 sudo apt-get install build-essential openssl libssl-dev libudev-dev
320 sudo ./parity-deploy.sh --config aura
321 sudo ./parity-deploy.sh --config aura --nodes 2 --ethstats
322 cargo build --release -p ethstore --features=ethstore-cli
323 sudo apt install cargo
324 docker run -it ubuntu bash
325 sudo docker run -it ubuntu bash
326 sudo curl https://sh.rustup.rs -sSf | sh
327 cd ..
328 git clone https://github.com/paritytech/parity
329 sudo git clone https://github.com/paritytech/parity
330 cd parity
331 git submodule init
332 sudo git submodule init
333 sudo git submodule update
334 sudo cargo build
335 ls
336 ./test.sh
337 sudo ./test.sh
338 sudo cargo test --release --features ethcore/json-tests -p ethcore
339 curl -s http://localhost:8180
340 sudo curl -s http://localhost:8180
341 sudo ./parity-deploy.sh --config aura --nodes 2 --ethstats
342 cd ..
343 sudo ./parity-deploy.sh --config aura --nodes 2 --ethstats
344 ls
345 cd parity-deploy/
346 ls
347 sudo ./parity-deploy.sh --config aura --nodes 2 --ethstats
348 sudo ./parity-deploy.sh -h
349 sudo ./parity-deploy.sh --config aura --nodes 2 --ethstats -expose 8180
350 sudo ./parity-deploy.sh --config aura --nodes 2 --ethstats -expose
351 sudo ./parity-deploy.sh
352 sudo ./parity-deploy.sh --config dev
353 lsb_release -a
354 history

Can anybody help me or have an idea why i always get the Result "read EC key" and nothing go further...

Cannot run a fresh install

Existing version of parity: 0.0.0 is newer than the version you attempting to install: 

and then parity-download.sh exists.

Attempting to install 2.3.3.

Inconsistent nomenclature of chain spec

I have studied the script and it looks amazing. However I have doubt regarding the configuration.

When the authority.toml file is generated, it specifies a chain = "/home/parity/chain.json". However, when the chain config is generated by the script, it is saved as spec.json (see here on line 347). Indeed, by inspecting the docker container (assuming just one node within the network) there is an inconsistency. The authority.toml looks for a chain.json config file, while in that folder is present a spec.json config file. This can be deduce also by the mapping [host:container] in docker services template

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.