Problems with setting up my own node

weeeeeeee4 · January 21, 2021, 8:34pm

Hi there,

After setting up a centrifuge node on windows, I wanted to try the install on a VPS with Ubuntu.

I´m using the bare metal instructions @ https://developer.centrifuge.io/chain/get-started/run-node/

But i get the following error at step 7:

root@ubuntu-xxx:~# git clone -b v2.0.0-rc6.0 git@github.com:centrifuge/centrifuge-chain.git
Cloning into 'centrifuge-chain'...
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Is the link maybe wrong or did I do something wrong?

Cheers,
weeeeeee

weeeeeeee4 · January 21, 2021, 8:39pm

Google helps

I tried “git clone -b v2.0.0-rc6.0 https://github.com/centrifuge/centrifuge-chain.git” and it worked!

weeeeeeee4 · January 21, 2021, 9:04pm

But new error coming up:

root@ubuntu-xxx:~/centrifuge-chain# cargo build --release

(…)
error: failed to run custom build command for centrifuge-chain-runtime v2.0.0 (/root/centrifuge-chain/runtime)

Caused by:
  process didn't exit successfully: `/root/centrifuge-chain/target/release/build/centrifuge-chain-runtime-378535fc647e1cde/build-script-build` (exit code: 1)
  --- stdout
  Executing build command: "rustup" "run" "nightly" "cargo" "rustc" "--target=wasm32-unknown-unknown" "--manifest-path=/root/centrifuge-chain/target/release/wbuild/centrifuge-chain-runtime/Cargo.toml" "--color=always" "--release"

  --- stderr

(…)

    Compiling finality-grandpa v0.12.3
      error[E0282]: type annotations needed
      --> /root/.cargo/git/checkouts/substrate-c08550cb428dbcc9/a67d1c1/primitives/arithmetic/src/fixed_point.rs:541:9
       |
      541  |                   let accuracy = P::ACCURACY.saturated_into();
       |                       ^^^^^^^^ consider giving `accuracy` a type
      ...
      1595 | / implement_fixed!(
      1596 | |     FixedI64,
      1597 | |     test_fixed_i64,
      1598 | |     i64,
      ...    |
      1601 | |     "_Fixed Point 64 bits signed, range = [-9223372036.854775808, 9223372036.854775807]_",
      1602 | | );
       | |__- in this macro invocation
       |
       = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

      error[E0282]: type annotations needed
      --> /root/.cargo/git/checkouts/substrate-c08550cb428dbcc9/a67d1c1/primitives/arithmetic/src/fixed_point.rs:541:9
       |
      541  |                   let accuracy = P::ACCURACY.saturated_into();
       |                       ^^^^^^^^ consider giving `accuracy` a type
      ...
      1604 | / implement_fixed!(
      1605 | |     FixedI128,
      1606 | |     test_fixed_i128,
      1607 | |     i128,
      ...    |
      1611 | |         [-170141183460469231731.687303715884105728, 170141183460469231731.687303715884105727]_",
      1612 | | );
       | |__- in this macro invocation
       |
       = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

      error[E0282]: type annotations needed
      --> /root/.cargo/git/checkouts/substrate-c08550cb428dbcc9/a67d1c1/primitives/arithmetic/src/fixed_point.rs:541:9
       |
      541  |                   let accuracy = P::ACCURACY.saturated_into();
       |                       ^^^^^^^^ consider giving `accuracy` a type
      ...
      1614 | / implement_fixed!(
      1615 | |     FixedU128,
      1616 | |     test_fixed_u128,
      1617 | |     u128,
      ...    |
      1621 | |         [0.000000000000000000, 340282366920938463463.374607431768211455]_",
      1622 | | );
       | |__- in this macro invocation
       |
       = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

      error: aborting due to 3 previous errors

      For more information about this error, try `rustc --explain E0282`.
      error: could not compile `sp-arithmetic`

      To learn more, run the command again with --verbose.
      warning: build failed, waiting for other jobs to finish...
      error: build failed
    warning: build failed, waiting for other jobs to finish...
    error: build failed

SOLVED I tried the second way to install nightly for WASM support and it the error is not coming up anymore

now working on:

warning: build/expando.c:4:24: error: pasting "RUST_VERSION_OPENSSL_" and "(" does not give a valid preprocessing token
warning:     4 | #define VERSION2(n, v) RUST_VERSION_##n##_##v
warning:       |                        ^~~~~~~~~~~~~
warning: build/expando.c:5:23: note: in expansion of macro ‘VERSION2’
warning:     5 | #define VERSION(n, v) VERSION2(n, v)
warning:       |                       ^~~~~~~~
warning: build/expando.c:10:1: note: in expansion of macro ‘VERSION’
warning:    10 | VERSION(OPENSSL, OPENSSL_VERSION_NUMBER)
warning:       | ^~~~~~~

error: failed to run custom build command for `openssl-sys v0.9.58`

Caused by:
  process didn't exit successfully: `/root/centrifuge-chain/target/release/build/openssl-sys-3a8763f3427fc6d4/build-script-main` (exit code: 101)
  --- stdout
  cargo:rustc-cfg=const_fn
  cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_GNU_OPENSSL_LIB_DIR
  X86_64_UNKNOWN_LINUX_GNU_OPENSSL_LIB_DIR unset
  cargo:rerun-if-env-changed=OPENSSL_LIB_DIR
  OPENSSL_LIB_DIR unset
  cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_GNU_OPENSSL_INCLUDE_DIR
  X86_64_UNKNOWN_LINUX_GNU_OPENSSL_INCLUDE_DIR unset
  cargo:rerun-if-env-changed=OPENSSL_INCLUDE_DIR
  OPENSSL_INCLUDE_DIR unset
  cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_GNU_OPENSSL_DIR
  X86_64_UNKNOWN_LINUX_GNU_OPENSSL_DIR unset
  cargo:rerun-if-env-changed=OPENSSL_DIR
  OPENSSL_DIR unset
  cargo:rerun-if-env-changed=OPENSSL_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=OPENSSL_STATIC
  cargo:rerun-if-env-changed=OPENSSL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=SYSROOT
  cargo:rerun-if-env-changed=OPENSSL_STATIC
  cargo:rerun-if-env-changed=OPENSSL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rustc-link-lib=ssl
  cargo:rustc-link-lib=crypto
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=OPENSSL_STATIC
  cargo:rerun-if-env-changed=OPENSSL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
  OPT_LEVEL = Some("3")
  TARGET = Some("x86_64-unknown-linux-gnu")
  HOST = Some("x86_64-unknown-linux-gnu")
  CC_x86_64-unknown-linux-gnu = None
  CC_x86_64_unknown_linux_gnu = None
  HOST_CC = None
  CC = None
  CFLAGS_x86_64-unknown-linux-gnu = None
  CFLAGS_x86_64_unknown_linux_gnu = None
  HOST_CFLAGS = None
  CFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  CARGO_CFG_TARGET_FEATURE = Some("fxsr,mmx,sse,sse2")
  running: "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-I" "/usr/include" "-Wall" "-Wextra" "-E" "build/expando.c"
  cargo:warning=build/expando.c:4:24: error: pasting "RUST_VERSION_OPENSSL_" and "(" does not give a valid preprocessing token
  cargo:warning=    4 | #define VERSION2(n, v) RUST_VERSION_##n##_##v
  cargo:warning=      |                        ^~~~~~~~~~~~~
  cargo:warning=build/expando.c:5:23: note: in expansion of macro ‘VERSION2’
  cargo:warning=    5 | #define VERSION(n, v) VERSION2(n, v)
  cargo:warning=      |                       ^~~~~~~~
  cargo:warning=build/expando.c:10:1: note: in expansion of macro ‘VERSION’
  cargo:warning=   10 | VERSION(OPENSSL, OPENSSL_VERSION_NUMBER)
  cargo:warning=      | ^~~~~~~
  exit code: 1

  --- stderr
  thread 'main' panicked at '
  Header expansion error:
  Error { kind: ToolExecError, message: "Command \"cc\" \"-O3\" \"-ffunction-sections\" \"-fdata-sections\" \"-fPIC\" \"-m64\" \"-I\" \"/usr/include\" \"-Wall\" \"-Wextra\" \"-E\" \"build/expando.c\" with args \"cc\" did not execute successfully (status code exit code: 1)." }

  Failed to find OpenSSL development headers.

What I tried so far:

apt-get install libssl-dev pkg-config > OpenSSL 1.1.1f is installed
the steps described here Build Substrate on Ubuntu: step-by-step guide | Alexander Gryaznov’s Blog
…more tomorrow

weeeeeeee4 · January 22, 2021, 8:11am

Same problem was mentioned @ https://centrifuge-io.slack.com/archives/CDSF7BLGK/p1610081730055900

will try later (probably with a new install as I tried a lot yesterday with trial and error):
rustup update nightly-2020-08-16
rustup toolchain install nightly-2020-08-16
rustup default nightly-2020-08-16
rustup target add wasm32-unknown-unknown --toolchain nightly-2020-08-16

weeeeeeee4 · February 1, 2021, 9:19pm

So finally I found time do fix this, also thanks to help in the centrifuge dev channel @ slack.

What seems to missing in the “run your own node” tutorial are the steps explained here (at least for my case): Installation · Substrate Developer Hub

My previous post here should be ignored as it is probably wrong

I did a complete reset of the VPS with a clean install and now my node is running and currently syncing

Topic		Replies	Views
Running my Own Mainnet Node using Docker Engineering	6	860	May 8, 2021
Running a Centrifuge node Engineering	10	797	January 22, 2021
Looking for a simple way to set up as a validator? Engineering	9	1410	January 28, 2021
Running a node? Engineering	6	514	October 19, 2021
Running a node on Centrifuge? Engineering	2	619	July 20, 2021

Problems with setting up my own node

Related topics