open-web3-stack / parachain-launch Goto Github PK

View Code? Open in Web Editor NEW

72.0 72.0 34.0 2.72 MB

Tool to generate docker-compose.yml to launch a full relaychain - parachain testnet.

License: Apache License 2.0

JavaScript 5.36% TypeScript 94.64%

docker polkadot-js substrate

parachain-launch's People

Contributors

Stargazers

Watchers

parachain-launch's Issues

nextFreeId seems wrong. still 2000.

I've deployed the system.
When I want to reserve a ParaId via the Polkadot Apps UI under the Parachains -> Parathreads tab, + ParaID button,
it pops out the default ParaId for me to reserve is still 2000, which is already taken by karura. so I got stuck here.

According to this explanation, "The Id of this parachain as known on the network (selected from nextFreeId)", I believe that nextFreeId on the network seems wrong.

Thx.

[feat] Use Polkadot UI

As suggested in the official Polkadot node documentation, one can set up a Grafana Dashboard for the node(s).
I was able to quickly set it up by adding the following into docker-compose.yaml:

services:
  # Polkadot UI: https://github.com/paritytech/polkadot/blob/master/doc/docker.md#using-docker-compose
  polkadotui:
    container_name: polkadotui
    image: jacogr/polkadot-js-apps
    environment:
      - WS_URL=ws://127.0.0.1:9944
    ports:
      - 8080:80

Is there a way to make this an option into this tool? Would it be nice to have?
If so, can we get some pointers from the contributors on how to implement it?

Error: Input("Error parsing spec file: unknown field `paraId` at line 239 column 1")

hello, update to polkadot:v0.9.13. i get some error with this update:

parachain-launch/src/index.ts

Line 311 in 0a1ff0f

spec.paraId = id;

trying to interact with polkadot.js

When I start the relay chains & the parachains locally and tried to interact via polkadot.js through e.g. ws://0.0.0.0:30333, the UI is stuck at initialization. Is there additional configuration I should do to make this work? I'm using the default configuration with Acala. Thanks!

Support for nodes that do not use substrate wallets (Moonbeam)

Hello, I have been trying to work out network containing Acala and Moonbeam however uppon compiling moonbeam I receive following error. My theory is that it is due to usage of different - ether style accounts. Thanks in advance

Support for env variables in image name

Currently facing the following issue:

This is the config.yaml file

# Relaychain Configuration
relaychain:
  image: parity/polkadot:v0.9.28
  chain: rococo-local
  runtimeGenesisConfig:
    configuration:
      config:
        validation_upgrade_cooldown: 10
        validation_upgrade_delay: 10
  env:
    RUST_LOG: parachain::candidate-backing=trace,parachain::candidate-selection=trace,parachain::pvf=trace,parachain::collator-protocol=trace,parachain::provisioner=trace
  flags:
    - --rpc-methods=unsafe
  nodes:
    - name: alice
      wsPort: 9944
      rpcPort: 9933
      port: 30333
      flags:
        - --force-authoring
      env:
        RUST_LOG: babe=debug
    - name: bob
    - name: charlie

# Parachain Configuration
parachains:
- image: ${DOCKER_IMAGE_PATH}:${DOCKER_IMAGE_TAG}  ## <-- The env for image ##
  chain:
    base: rocfinity-local
  id: 2021
  parachain: true
  flags:
    - --force-authoring
    - --rpc-methods=unsafe
    - --execution=wasm
  relaychainFlags:
    - --execution=wasm
    - --port=30343
    - --rpc-methods=Auto
  env:
    RUST_LOG: runtime=debug,sc_basic_authorship=trace,cumulus-consensus=trace,cumulus-collator=trace,collator_protocol=trace,collation_generation=trace,aura=debug,pallet-collator-staking=trace,xcm=trace,pallet-xcm=trace
  volumePath: /data
  nodes:
  - wsPort: 10010
    rpcPort: 10011
    port: 40334
    flags:
      - --alice
  - wsPort: 10012
    rpcPort: 10013
    port: 40335
    flags:
      - --bob

When running ./node_modules/@open-web3/parachain-launch/bin/parachain-launch generate -y configs/config.yaml, it produces the following file

FROM ${DOCKER_IMAGE_PATH}:${DOCKER_IMAGE_TAG}
COPY . /app

and this results in an error since the ARGS are not added to the dockerfile from here

Is it possible to do this any other way? Or is this possible only with a change in the code to support passing ARGS?

Kusama testnet config

Create a config file that:

Use kusama-dev
Includes Karura
Includes Bifrost
Create HRMP channels on genesis

Where is the genesis file

I saw the genesis field in generated .json file, but not sure it's what I want. What I'm trying to do is register para chain which needs to submit a genesis file and validation code

support parachain which doesn't have key command

statemine doesn't have key command, since we only use key command for node-key generation, maybe we can use other chains instead of the parachain itself.

Error on unknown argument

Should detect unknown argument and exit error

Update NextFreeParaId

When paritytech/polkadot#3781 is released

Support other "collators" pallets

I've quickly tried to add Moonbeam as a config, however there are multiple issues:

"sudo" convert to ss58 when using "alice" or if provided the hex representation fails with:

Input("Error parsing spec file: invalid length 48, expected a (both 0x-prefixed or not) hex string with length of 40 at line 32 column 62")\

"collators" is expecting "collatorSelection" in the genesis, while some other parachain are using other pallet (ex: "parachainStaking")

Overall, I think having the possibility to modify the pallet genesis directly by specifyin the pallet and field name in the yml file directly would be more flexible.

What's your opinion ?

parity/polkadot:v0.9.16

$ docker run --rm -v "/tmp/rococo-local.json":/rococo-local.json parity/polkadot:v0.9.16 build-spec --raw --chain=/rococo-local.json --disable-default-bootnode > output/rococo-local.json
Error: Command failed with code 1
[String: ''] {
  stdout: '',
  stderr: '2022-02-11 09:03:07 Building chain spec    \n' +
    'Error: \n' +
    '   0: \x1B[91mOther: Error parsing spec file: duplicate field `validation_upgrade_cooldown` at line 187 column 43\x1B[0m\n' +
    '\n' +
    '  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n' +
    '   1: \x1B[32m__libc_start_main\x1B[0m\x1B[90m<unknown>\x1B[0m\n' +
    '      at \x1B[35m<unknown source file>\x1B[0m:\x1B[35m<unknown line>\x1B[0m\n' +
    '\n' +
    'Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.\n' +
    'Run with RUST_BACKTRACE=full to include source snippets.\n',
  code: 1,
  cat: [Function: bound ],
  exec: [Function: bound ],
  grep: [Function: bound ],
  head: [Function: bound ],
  sed: [Function: bound ],
  sort: [Function: bound ],
  tail: [Function: bound ],
  to: [Function: bound ],
  toEnd: [Function: bound ],
  uniq: [Function: bound ]
}
error Command failed with exit code 1.```

support balance >= 1e21

currently parachain-launch will not be able to support balance >= 1e21 due to JS behaviour:

console.log(JSON.stringify(10 ** 20)) // 100000000000000000000

console.log(JSON.stringify(10 ** 21)) // 1e+21

serde_json can parse 100000000000000000000 but not 1e+21, which means if we have a balance bigger than 1e21 then parachain-launch will create invalid chainspec json (which cannot be imported by serde_json)

[Question] Leases number setting

Hey!
Is there a way to set the number of leases a parachain will live?
Thanks!

jsonStringify bug

const jsonStringify = (spec: any) =>
  // JSON.stringify will serialize big number to scientific notation such as 1e+21, which is not supported by Substrate
  JSON.stringify(spec, (_, v) => (typeof v === 'number' ? `@${BigInt(v).toString()}@` : v), 2).replace(
    /"@(.*?)@"/g,
    '$1',
  );

const balances = 2000000000000000000000000;

console.log(jsonStringify(balances));

1999999999999999966445568

w

Allow unsafe rpc-methods

--rpc-methods=Unsafe

Allow override general council and technical council

So we can trigger runtime upgrade via democracy without sudo

Multi-relaychain support with their own parachains

This can be a good feature to implement when we would like to test both Kusama and Polkadot, so it looks like:

kusama:

statemine
parachain1
parachain2
..

polkadot:

statemint
parachain1
parachain2
..

This can be useful to implement if someone finds time to do it

Occasionally error: The WASM interface has not been initialized

See litentry/litentry-parachain#1364

In our recent CIs, parachain-launch gives out errors when generating the relaychain genesis files, stack trace:

Trace: Error: Error: The WASM interface has not been initialized. Ensure that you wait for the initialization Promise with waitReady() from @polkadot/wasm-crypto (or cryptoWaitReady() from @polkadot/util-crypto) before attempting to use WASM-only interfaces.
    at /home/runner/work/litentry-parachain/litentry-parachain/docker/node_modules/@polkadot/wasm-crypto/cjs/bundle.js:46:13
    at sr25519PairFromSeed (/home/runner/work/litentry-parachain/litentry-parachain/docker/node_modules/@polkadot/util-crypto/cjs/sr25519/pair/fromSeed.js:22:82)
    at Object.sr25519 (/home/runner/work/litentry-parachain/litentry-parachain/docker/node_modules/@polkadot/keyring/cjs/keyring.js:19:56)
    at Keyring.createFromUri (/home/runner/work/litentry-parachain/litentry-parachain/docker/node_modules/@polkadot/keyring/cjs/keyring.js:256:115)
    at generateRelaychainGenesisFile (/home/runner/work/litentry-parachain/litentry-parachain/docker/node_modules/@open-web3/parachain-launch/lib/index.js:1[43](https://github.com/litentry/litentry-parachain/actions/runs/4250721399/jobs/7393584955#step:8:44):31)
    at generate (/home/runner/work/litentry-parachain/litentry-parachain/docker/node_modules/@open-web3/parachain-launch/lib/index.js:374:5)
    at fatal (/home/runner/work/litentry-parachain/litentry-parachain/docker/node_modules/@open-web3/parachain-launch/lib/index.js:55:13)
make: *** [Makefile:175: generate-docker-compose-rococo] Error 1

Strangely it only happens sometimes, and only recently, maybe have you got a quick idea what's happening? Version/dependency problem?

We have been using the latest parachain-launch (1.2.2) for a long time, and this is our parachain-launch config.
Thanks for any help!

Running polkadot 110 but chain at 9430 ?

Hi!
When running one of the examples ( ie relayChain )
Evth goes fine, but when checking the relay-state, it prints 94.3.0
From rococo I can see that
specVersion: 1,006,002
But locally I would expect 1,001,000
but getting 9430 on rpc -> getRuntimeVersion

{
  specName: rococo
  implName: parity-rococo-v2.0
  authoringVersion: 0
  specVersion: 9,430
  implVersion: 0

Relay dockerFile seems to be fine:

 cat relaychain.Dockerfile                                                                                   ✔ 
FROM parity/polkadot:v1.1.0
COPY . /app%

And the image seems to be fine too

 docker run -it --entrypoint=/bin/bash parity/polkadot:v1.1.0                                           
parity@4621751af236:/$ /usr/bin/polkadot --version
polkadot 1.1.0-f60318f6868

running 2.0 version :
npx @open-web3/parachain-launch --version --> 2.0.0

How to reproduce:

rm -rf output ; npx @open-web3/parachain-launch generate acala.yml --yes
cd output ; docker compose up -d --build
go to : https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/
Check that runtime version is not 110 on rpc-> state > getRuntimeVersion

Thankss!!

Allow specify genesis balances

So we can have more test tokens for testing.

support port start index

sometimes we may want to launch two testnets on the same machine, one for polkadot-local + acala for example, another for kusama-local + karura for example.

since we cannot use one config.yml for launching them all together, I'm wondering if we can support start index

https://github.com/open-web3-stack/parachain-launch/blob/master/src/index.ts#L458

Be able to specify both runtime and client versions

In order to perform upgrade tests, it would be useful to be able to specify separate runtime and client versions on a built chain.

For example:

Acala Node, Client version: 2.4.0
Acala Chain, Spec version: 2.3.3

Currently when using the generate CLI command, only the most uptodate chain data is generated for that docker image e.g. - image: acala/acala-node:2.4.0

Running parachain-launch on Apple Silicon

When I run the docker-compose up -d --build command, the Polkadot images work fine, but the 2 out of the 3 Acala images do not run:

$ docker ps -a
CONTAINER ID   IMAGE                       COMMAND                  CREATED         STATUS                     PORTS                                                                      NAMES
cf8aec52a283   output_parachain-2000-0     "/usr/local/bin/acal…"   3 minutes ago   Up 3 minutes               0.0.0.0:9936->9933/tcp, 0.0.0.0:9947->9944/tcp, 0.0.0.0:30336->30333/tcp   output-parachain-2000-0-1
664197820ec8   output_relaychain-bob       "/usr/bin/polkadot -…"   3 minutes ago   Up 3 minutes               0.0.0.0:9934->9933/tcp, 0.0.0.0:9945->9944/tcp, 0.0.0.0:30334->30333/tcp   output-relaychain-bob-1
b80222bc128b   output_parachain-2000-2     "/usr/local/bin/acal…"   3 minutes ago   Exited (2) 3 minutes ago                                                                              output-parachain-2000-2-1
007ab5dd6c15   output_relaychain-charlie   "/usr/bin/polkadot -…"   3 minutes ago   Up 3 minutes               0.0.0.0:9935->9933/tcp, 0.0.0.0:9946->9944/tcp, 0.0.0.0:30335->30333/tcp   output-relaychain-charlie-1
ffaa94943ef1   output_relaychain-alice     "/usr/bin/polkadot -…"   3 minutes ago   Up 3 minutes               0.0.0.0:9933->9933/tcp, 0.0.0.0:9944->9944/tcp, 0.0.0.0:30333->30333/tcp   output-relaychain-alice-1
cbe6f641fce4   output_parachain-2000-1     "/usr/local/bin/acal…"   3 minutes ago   Exited (2) 3 minutes ago                                                                              output-parachain-2000-1-1

Logs say:

$ docker logs -f b80222bc128b
error: Invalid value "/dns/parachain-2000-0/tcp/30333/p2p/WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested\n12D3KooWAJjN3wDrpubrBwHQqgnNrM1rHanmKScCJ4jMqhc3FFMd" for '--bootnodes <ADDR>...': failed to parse: provided string contained invalid character 'I' at byte 4

Is there a way to request an Acala image that will run on my MacBook Pro?

Allow run only relaychain without any parachains

sometimes for test purpose, it can be good to run only relaychain testnet then add parachain later through extrinsics.

how to set different port for different node?

My test node already took 9944, so the alice will fail.

Successfully built ade9e97efc96
Successfully tagged output_parachain-2000-2:latest
Creating output_relaychain-alice_1 ...
Creating output_relaychain-alice_1   ... error
Creating output_parachain-2000-2_1   ...
Creating output_relaychain-bob_1     ...
Creating output_parachain-2000-0_1   ...
Creating output_relaychain-charlie_1 ... done
Creating output_parachain-2000-2_1   ... done
Creating output_relaychain-bob_1     ... done
Creating output_parachain-2000-0_1   ... done
Creating output_parachain-2000-1_1   ... done

ERROR: for relaychain-alice  Cannot start service relaychain-alice: driver failed programming external connectivity on endpoint output_relaychain-alice_1 (676ada3124c18e8788fca06873bd7a8c1c534736f6a0d07e39babdb26d49963f): Error starting userland proxy: listen tcp4 0.0.0.0:9944: bind: address already in use

Support for extra images

It would be nice to be able to specify some additional services that are not substrate-based nodes to run alongside what can now be configured. For example, being able to run the polkadot-js explorer.

This can be achieved by concatenating to the generated docker-compose file but it still would be nice to have this in config.yml since the output directory is not checked into git.

Support for M1/M2 Macbooks

Hi, our project that uses your library to start up the network has an issue where on M1/M2 MacBooks docker quits all containers shortly after launching. Was wondering if it is something regarding the broken library that parachain-launch uses or some library that does not support m1/m2 and if it can be resolved. It would be helpful. Currently, M platform is the way to go for future MacBooks so support is necessary. Many thanks for any kind of info.

This issue is mentioned here: w3f/Grant-Milestone-Delivery#584 (comment)
And we also have it as an issue here: https://github.com/paraspell/ui/issues/7
We have also tested it on M1 MacBook and the result was the same.

With kind regards,
Dudo

Make volume and base path configurable

Statemint fails to start

When trying to run a statemint parachain on a rococo-local relaychain, the parachain nodes fail to start.

Config:

# Relaychain Configuration
relaychain:
  image: parity/polkadot:v0.9.26
  chain: rococo-local
  runtimeGenesisConfig:
    configuration:
      config:
        validation_upgrade_cooldown: 10
        validation_upgrade_delay: 10
  hrmp:
    preopenHrmpChannels:
      - sender: 2000
        recipient: 2021
        maxCapacity: 8
        maxMessageSize: 102400
      - sender: 2021
        recipient: 2000
        maxCapacity: 8
        maxMessageSize: 102400
  env:
    RUST_LOG: parachain::candidate-backing=trace,parachain::candidate-selection=trace,parachain::pvf=trace,parachain::collator-protocol=trace,parachain::provisioner=trace
  flags:
    - --rpc-methods=unsafe
  nodes:
    - name: alice
      wsPort: 9944
      rpcPort: 9933
      port: 30333
      flags:
        - --force-authoring
      env:
        RUST_LOG: babe=debug
    - name: bob

# Parachain Configuration
parachains:
######################################
# STATEMINT
######################################
- image: parity/polkadot-parachain:0.9.230
  chain:
    base: statemint-local
  id: 1000
  parachain: true
  flags:
    - --force-authoring
    - --rpc-methods=unsafe
    - --execution=wasm
  relaychainFlags:
    - --execution=wasm
    - --port=30347
    - --rpc-methods=Auto
  volumePath: /statemint/data
  nodes:
  - wsPort: 10030
    rpcPort: 10031
    port: 30337
    flags:
      - --alice
  - flags:
    - --bob

Running parachain-launch/bin/parachain-launch generate -y config-statemint.yaml would generate the required output files. However, the following error is shown as soon as the parachain nodes start:

parachain-1000-0_1  | 2022-08-11 15:57:44 Failed to run the sequential write disk benchmark: failed to create a test file: No such file or directory (os error 2)
parachain-1000-0_1  | 2022-08-11 15:57:44 Failed to run the random write disk benchmark: failed to create a test file: No such file or directory (os error 2)
parachain-1000-1_1  | 2022-08-11 15:57:44 Failed to run the sequential write disk benchmark: failed to create a test file: No such file or directory (os error 2)
parachain-1000-0_1  | Error: Service(Keystore(Io(Os { code: 13, kind: PermissionDenied, message: "Permission denied" })))
parachain-1000-0_1  | 2022-08-11 15:57:44 assembling new collators for new session 0 at #0
parachain-1000-0_1  | 2022-08-11 15:57:44 assembling new collators for new session 1 at #0
parachain-1000-0_1  | 2022-08-11 15:57:44 Parachain id: Id(1000)
parachain-1000-0_1  | 2022-08-11 15:57:44 Parachain Account: 5Ec4AhPZk8STuex8Wsi9TwDtJQxKqzPJRCH7348Xtcs9vZLJ
parachain-1000-0_1  | 2022-08-11 15:57:44 Parachain genesis state: 0x00000000000000000000000000000000000000000000000000000000000000000082825f73d38d68d3984b009f48799d59964bab0c17f1a0ae4e08e54f48b402db03170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400
parachain-1000-0_1  | 2022-08-11 15:57:44 Is collating: yes
parachain-1000-1_1  | 2022-08-11 15:57:44 Failed to run the random write disk benchmark: failed to create a test file: No such file or directory (os error 2)
parachain-1000-1_1  | Error: Service(Keystore(Io(Os { code: 13, kind: PermissionDenied, message: "Permission denied" })))
parachain-1000-1_1  | 2022-08-11 15:57:44 assembling new collators for new session 0 at #0
parachain-1000-1_1  | 2022-08-11 15:57:44 assembling new collators for new session 1 at #0
parachain-1000-1_1  | 2022-08-11 15:57:44 Parachain id: Id(1000)
parachain-1000-1_1  | 2022-08-11 15:57:44 Parachain Account: 5Ec4AhPZk8STuex8Wsi9TwDtJQxKqzPJRCH7348Xtcs9vZLJ
parachain-1000-1_1  | 2022-08-11 15:57:44 Parachain genesis state: 0x00000000000000000000000000000000000000000000000000000000000000000082825f73d38d68d3984b009f48799d59964bab0c17f1a0ae4e08e54f48b402db03170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400
parachain-1000-1_1  | 2022-08-11 15:57:44 Is collating: yes
output_parachain-1000-0_1 exited with code 1
output_parachain-1000-1_1 exited with code 1

Full log until terminated:

Creating output_relaychain-bob_1   ... done
Creating output_parachain-1000-0_1 ... done
Creating output_parachain-1000-1_1 ... done
Creating output_relaychain-alice_1 ... done
Attaching to output_parachain-1000-0_1, output_parachain-1000-1_1, output_relaychain-alice_1, output_relaychain-bob_1
parachain-1000-0_1  | 2022-08-11 15:57:43 Polkadot parachain
parachain-1000-0_1  | 2022-08-11 15:57:43 ✌️  version 0.9.230-7f8f20b3513
parachain-1000-0_1  | 2022-08-11 15:57:43 ❤️  by Parity Technologies <[email protected]>, 2017-2022
parachain-1000-0_1  | 2022-08-11 15:57:43 📋 Chain specification: Statemint Local
parachain-1000-0_1  | 2022-08-11 15:57:43 🏷  Node name: parachain-1000-0
parachain-1000-0_1  | 2022-08-11 15:57:43 👤 Role: AUTHORITY
parachain-1000-0_1  | 2022-08-11 15:57:43 💾 Database: RocksDb at /statemint/data/chains/statemint_local/db/full
parachain-1000-0_1  | 2022-08-11 15:57:43 ⛓  Native runtime: statemint-9230 (statemint-0.tx7.au1)
parachain-1000-1_1  | 2022-08-11 15:57:44 Polkadot parachain
parachain-1000-1_1  | 2022-08-11 15:57:44 ✌️  version 0.9.230-7f8f20b3513
parachain-1000-1_1  | 2022-08-11 15:57:44 ❤️  by Parity Technologies <[email protected]>, 2017-2022
parachain-1000-1_1  | 2022-08-11 15:57:44 📋 Chain specification: Statemint Local
parachain-1000-1_1  | 2022-08-11 15:57:44 🏷  Node name: parachain-1000-1
parachain-1000-1_1  | 2022-08-11 15:57:44 👤 Role: AUTHORITY
parachain-1000-1_1  | 2022-08-11 15:57:44 💾 Database: RocksDb at /statemint/data/chains/statemint_local/db/full
parachain-1000-1_1  | 2022-08-11 15:57:44 ⛓  Native runtime: statemint-9230 (statemint-0.tx7.au1)
relaychain-alice_1  | 2022-08-11 15:57:44.064  INFO main sc_cli::runner: Parity Polkadot
relaychain-alice_1  | 2022-08-11 15:57:44.065  INFO main sc_cli::runner: ✌️  version 0.9.26-d8785970175
relaychain-alice_1  | 2022-08-11 15:57:44.065  INFO main sc_cli::runner: ❤️  by Parity Technologies <[email protected]>, 2017-2022
relaychain-alice_1  | 2022-08-11 15:57:44.065  INFO main sc_cli::runner: 📋 Chain specification: Rococo Local Testnet
relaychain-alice_1  | 2022-08-11 15:57:44.065  INFO main sc_cli::runner: 🏷  Node name: alice
relaychain-alice_1  | 2022-08-11 15:57:44.065  INFO main sc_cli::runner: 👤 Role: AUTHORITY
relaychain-alice_1  | 2022-08-11 15:57:44.065  INFO main sc_cli::runner: 💾 Database: RocksDb at /data/chains/rococo_local_testnet/db/full
relaychain-alice_1  | 2022-08-11 15:57:44.065  INFO main sc_cli::runner: ⛓  Native runtime: rococo-9260 (parity-rococo-v2.0-0.tx1.au0)
relaychain-bob_1    | 2022-08-11 15:57:44.072  INFO main sc_cli::runner: Parity Polkadot
relaychain-bob_1    | 2022-08-11 15:57:44.072  INFO main sc_cli::runner: ✌️  version 0.9.26-d8785970175
relaychain-bob_1    | 2022-08-11 15:57:44.072  INFO main sc_cli::runner: ❤️  by Parity Technologies <[email protected]>, 2017-2022
relaychain-bob_1    | 2022-08-11 15:57:44.072  INFO main sc_cli::runner: 📋 Chain specification: Rococo Local Testnet
relaychain-bob_1    | 2022-08-11 15:57:44.072  INFO main sc_cli::runner: 🏷  Node name: bob
relaychain-bob_1    | 2022-08-11 15:57:44.072  INFO main sc_cli::runner: 👤 Role: AUTHORITY
relaychain-bob_1    | 2022-08-11 15:57:44.072  INFO main sc_cli::runner: 💾 Database: RocksDb at /data/chains/rococo_local_testnet/db/full
relaychain-bob_1    | 2022-08-11 15:57:44.072  INFO main sc_cli::runner: ⛓  Native runtime: rococo-9260 (parity-rococo-v2.0-0.tx1.au0)
parachain-1000-0_1  | 2022-08-11 15:57:44 Failed to run the sequential write disk benchmark: failed to create a test file: No such file or directory (os error 2)
parachain-1000-0_1  | 2022-08-11 15:57:44 Failed to run the random write disk benchmark: failed to create a test file: No such file or directory (os error 2)
parachain-1000-1_1  | 2022-08-11 15:57:44 Failed to run the sequential write disk benchmark: failed to create a test file: No such file or directory (os error 2)
parachain-1000-0_1  | Error: Service(Keystore(Io(Os { code: 13, kind: PermissionDenied, message: "Permission denied" })))
parachain-1000-0_1  | 2022-08-11 15:57:44 assembling new collators for new session 0 at #0
parachain-1000-0_1  | 2022-08-11 15:57:44 assembling new collators for new session 1 at #0
parachain-1000-0_1  | 2022-08-11 15:57:44 Parachain id: Id(1000)
parachain-1000-0_1  | 2022-08-11 15:57:44 Parachain Account: 5Ec4AhPZk8STuex8Wsi9TwDtJQxKqzPJRCH7348Xtcs9vZLJ
parachain-1000-0_1  | 2022-08-11 15:57:44 Parachain genesis state: 0x00000000000000000000000000000000000000000000000000000000000000000082825f73d38d68d3984b009f48799d59964bab0c17f1a0ae4e08e54f48b402db03170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400
parachain-1000-0_1  | 2022-08-11 15:57:44 Is collating: yes
parachain-1000-1_1  | 2022-08-11 15:57:44 Failed to run the random write disk benchmark: failed to create a test file: No such file or directory (os error 2)
parachain-1000-1_1  | Error: Service(Keystore(Io(Os { code: 13, kind: PermissionDenied, message: "Permission denied" })))
parachain-1000-1_1  | 2022-08-11 15:57:44 assembling new collators for new session 0 at #0
parachain-1000-1_1  | 2022-08-11 15:57:44 assembling new collators for new session 1 at #0
parachain-1000-1_1  | 2022-08-11 15:57:44 Parachain id: Id(1000)
parachain-1000-1_1  | 2022-08-11 15:57:44 Parachain Account: 5Ec4AhPZk8STuex8Wsi9TwDtJQxKqzPJRCH7348Xtcs9vZLJ
parachain-1000-1_1  | 2022-08-11 15:57:44 Parachain genesis state: 0x00000000000000000000000000000000000000000000000000000000000000000082825f73d38d68d3984b009f48799d59964bab0c17f1a0ae4e08e54f48b402db03170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400
parachain-1000-1_1  | 2022-08-11 15:57:44 Is collating: yes
output_parachain-1000-0_1 exited with code 1
output_parachain-1000-1_1 exited with code 1
relaychain-bob_1    | 2022-08-11 15:57:46.806  INFO main sc_service::client::client: 🔨 Initializing Genesis block/state (state: 0x2b14…5319, header-hash: 0xb6c9…aa29)
relaychain-bob_1    | 2022-08-11 15:57:46.815  INFO main afg: 👴 Loading GRANDPA authority set from genesis on what appears to be first startup.
relaychain-alice_1  | 2022-08-11 15:57:46.999  INFO main sc_service::client::client: 🔨 Initializing Genesis block/state (state: 0x2b14…5319, header-hash: 0xb6c9…aa29)
relaychain-alice_1  | 2022-08-11 15:57:47.007  INFO main afg: 👴 Loading GRANDPA authority set from genesis on what appears to be first startup.
relaychain-bob_1    | 2022-08-11 15:57:47.237  INFO main babe: 👶 Creating empty BABE epoch changes on what appears to be first startup.
relaychain-bob_1    | 2022-08-11 15:57:47.238  INFO main sub-libp2p: 🏷  Local node identity is: 12D3KooWFmasu1eVGSSyhDF6FxU9h1pqtbZQbFCnAe7GKvummuUa
relaychain-alice_1  | 2022-08-11 15:57:47.303  INFO main babe: 👶 Creating empty BABE epoch changes on what appears to be first startup.
relaychain-alice_1  | 2022-08-11 15:57:47.303  INFO main sub-libp2p: 🏷  Local node identity is: 12D3KooWHdRqGW7RAaBm7q6ac21sEYzipxkE4PMsy6myKCguQMLj
relaychain-bob_1    | 2022-08-11 15:57:47.590  INFO main sc_sysinfo: 💻 Operating system: linux
relaychain-bob_1    | 2022-08-11 15:57:47.590  INFO main sc_sysinfo: 💻 CPU architecture: x86_64
relaychain-bob_1    | 2022-08-11 15:57:47.590  INFO main sc_sysinfo: 💻 Target environment: gnu
relaychain-bob_1    | 2022-08-11 15:57:47.590  INFO main sc_sysinfo: 💻 CPU: 12th Gen Intel(R) Core(TM) i9-12900K
relaychain-bob_1    | 2022-08-11 15:57:47.590  INFO main sc_sysinfo: 💻 CPU cores: 16
relaychain-bob_1    | 2022-08-11 15:57:47.590  INFO main sc_sysinfo: 💻 Memory: 64060MB
relaychain-bob_1    | 2022-08-11 15:57:47.590  INFO main sc_sysinfo: 💻 Kernel: 5.15.59
relaychain-bob_1    | 2022-08-11 15:57:47.590  INFO main sc_sysinfo: 💻 Linux distribution: Ubuntu 20.04.4 LTS
relaychain-bob_1    | 2022-08-11 15:57:47.590  INFO main sc_sysinfo: 💻 Virtual machine: no
relaychain-bob_1    | 2022-08-11 15:57:47.590  INFO main sc_service::builder: 📦 Highest known block at #0
relaychain-bob_1    | 2022-08-11 15:57:47.590  INFO tokio-runtime-worker substrate_prometheus_endpoint: 〽️ Prometheus exporter started at 127.0.0.1:9615
relaychain-bob_1    | 2022-08-11 15:57:47.591  INFO                 main sc_rpc_server: Running JSON-RPC HTTP server: addr=0.0.0.0:9933, allowed origins=None
relaychain-bob_1    | 2022-08-11 15:57:47.591  INFO                 main sc_rpc_server: Running JSON-RPC WS server: addr=0.0.0.0:9944, allowed origins=None
relaychain-bob_1    | 2022-08-11 15:57:47.591  INFO                 main sc_sysinfo: 🏁 CPU score: 1301MB/s
relaychain-bob_1    | 2022-08-11 15:57:47.591  INFO                 main sc_sysinfo: 🏁 Memory score: 8010MB/s
relaychain-bob_1    | 2022-08-11 15:57:47.591  INFO                 main sc_sysinfo: 🏁 Disk score (seq. writes): 1363MB/s
relaychain-bob_1    | 2022-08-11 15:57:47.591  INFO                 main sc_sysinfo: 🏁 Disk score (rand. writes): 616MB/s
relaychain-bob_1    | 2022-08-11 15:57:47.591  INFO                 main babe: 👶 Starting BABE Authorship worker
relaychain-bob_1    | 2022-08-11 15:57:47.592  INFO tokio-runtime-worker libp2p_mdns::behaviour::iface: creating instance on iface 172.19.0.4
relaychain-bob_1    | 2022-08-11 15:57:47.594 TRACE tokio-runtime-worker parachain::collator-protocol: received a message msg=NetworkBridgeUpdate(OurViewChange(OurView { view: View { heads: [0xb6c91736ccf75376f1fdcb37227cf7745f42f70e4963fce1427e0d4a0c88aa29], finalized_number: 0 }, span_per_head: {0xb6c91736ccf75376f1fdcb37227cf7745f42f70e4963fce1427e0d4a0c88aa29: <jaeger span>} }))
relaychain-bob_1    | 2022-08-11 15:57:47.602 TRACE tokio-runtime-worker parachain::collator-protocol: Not a validator relay_parent=0xb6c91736ccf75376f1fdcb37227cf7745f42f70e4963fce1427e0d4a0c88aa29
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO main sc_sysinfo: 💻 Operating system: linux
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO main sc_sysinfo: 💻 CPU architecture: x86_64
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO main sc_sysinfo: 💻 Target environment: gnu
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO main sc_sysinfo: 💻 CPU: 12th Gen Intel(R) Core(TM) i9-12900K
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO main sc_sysinfo: 💻 CPU cores: 16
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO main sc_sysinfo: 💻 Memory: 64060MB
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO main sc_sysinfo: 💻 Kernel: 5.15.59
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO main sc_sysinfo: 💻 Linux distribution: Ubuntu 20.04.4 LTS
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO main sc_sysinfo: 💻 Virtual machine: no
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO main sc_service::builder: 📦 Highest known block at #0
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO tokio-runtime-worker substrate_prometheus_endpoint: 〽️ Prometheus exporter started at 127.0.0.1:9615
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO                 main sc_rpc_server: Running JSON-RPC HTTP server: addr=0.0.0.0:9933, allowed origins=None
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO                 main sc_rpc_server: Running JSON-RPC WS server: addr=0.0.0.0:9944, allowed origins=None
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO                 main sc_sysinfo: 🏁 CPU score: 1342MB/s
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO                 main sc_sysinfo: 🏁 Memory score: 7013MB/s
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO                 main sc_sysinfo: 🏁 Disk score (seq. writes): 1352MB/s
relaychain-alice_1  | 2022-08-11 15:57:47.653  INFO                 main sc_sysinfo: 🏁 Disk score (rand. writes): 615MB/s
relaychain-alice_1  | 2022-08-11 15:57:47.654  INFO                 main babe: 👶 Starting BABE Authorship worker
relaychain-alice_1  | 2022-08-11 15:57:47.654  INFO tokio-runtime-worker libp2p_mdns::behaviour::iface: creating instance on iface 172.19.0.5
relaychain-alice_1  | 2022-08-11 15:57:47.657  INFO tokio-runtime-worker libp2p_mdns::behaviour: discovered: 12D3KooWFmasu1eVGSSyhDF6FxU9h1pqtbZQbFCnAe7GKvummuUa /ip4/172.19.0.4/tcp/30333
relaychain-alice_1  | 2022-08-11 15:57:47.657  INFO tokio-runtime-worker libp2p_mdns::behaviour: discovered: 12D3KooWFmasu1eVGSSyhDF6FxU9h1pqtbZQbFCnAe7GKvummuUa /ip4/127.0.0.1/tcp/30333
relaychain-bob_1    | 2022-08-11 15:57:47.658  INFO tokio-runtime-worker libp2p_mdns::behaviour: discovered: 12D3KooWHdRqGW7RAaBm7q6ac21sEYzipxkE4PMsy6myKCguQMLj /ip4/172.19.0.5/tcp/30333
relaychain-bob_1    | 2022-08-11 15:57:47.658  INFO tokio-runtime-worker libp2p_mdns::behaviour: discovered: 12D3KooWHdRqGW7RAaBm7q6ac21sEYzipxkE4PMsy6myKCguQMLj /ip4/127.0.0.1/tcp/30333
^CGracefully stopping... (press Ctrl+C again to force)
Stopping output_relaychain-alice_1 ... done
Stopping output_relaychain-bob_1   ... done

open-web3-stack / parachain-launch Goto Github PK

parachain-launch's People

Contributors

Stargazers

Watchers

Forkers

parachain-launch's Issues

Recommend Projects

Recommend Topics

Recommend Org