[Guide] FULL NODE OpenSUSE 15.3: bitcoind + electrs + c-lightning + RTL

[BlackHatCoiner]

Thanks to n0nce who helped me in PMs! I now have my Lightning node working with RTL!

[1714862592]

1714862592

[1714862592]

1714862592

[1714862592]

1714862592

[1714862592]

1714862592

[1714862592]

1714862592

[n0nce]

Thanks to n0nce who helped me in PMs! I now have my Lightning node working with RTL!

Just 1 thing to point out here for other readers: there was no issue with the guide; it should still be possible to follow it line by line and get everything working without problem.
In BlackHatCoiner's case it was simply stuff like permissions and group memberships which were different due to him running Debian instead of OpenSUSE and in general only having followed parts of the guide opposed to the whole thing; so some tweaks had to be made here and there.

[cygan]

as you have already seen and read here👉https://bitcointalk.org/index.php?topic=5356129.msg59271490#msg59271490, i have installed 2 rpi 4 in my triton case ... on the one runs the umbrel full node and what should be operated on the second rpi 4, i am still undecided and would like to read from you a few suggestions and opinions...
what would be in mind that i already run 2 full nodes on the second rpi 4 useful to install and start?

since in the actual thread still no one has reacted to my post, i quote my message and post it here in the higher-frequented thread with the hope to still get good suggestions

[vv181]

Would like to make a suggestion regarding Tor configuration.
It's just a bit for improved privacy which is to uncomment the following line in /etc/tor/torrc

Code:

ExitPolicy reject *:*

~

Thanks, but I did include it exactly because of this already!

[6] Add the following contents, preferably in the right section (somewhere where there's HiddenServiceDir stuff commented out).

Code:

HiddenServiceDir /var/lib/tor/electrs_hidden_service/
HiddenServiceVersion 3
HiddenServicePort 50001 127.0.0.1:50001

ExitPolicy reject *:* # no exits allowed

Just curious, wouldn't that config has no effect since the default torrc configuration isn't technically enabled your node as a Tor exit relay and by default Tor already rejects it as a default config? or is there something to do with running the hidden service?

[n0nce]

~ snip ~

Just curious, wouldn't that config has no effect since the default torrc configuration isn't technically enabled your node as a Tor exit relay and by default Tor already rejects it as a default config? or is there something to do with running the hidden service?

If that's the default config, then I reckon it's not needed. But better to have it than not; maybe default value will change in the future, so specifying it directly isn't a bad idea in general.
Creating a hidden service shouldn't set you up as an exit node, if that's not the default.

[n0nce]

Little bump / PSA in case anyone is running this config / openSUSE node like me.

Since I chose to use Tor for the 'user facing' connections to the node, and because of the recent Tor vulnerability TROVE-2022-001 / CVE-2021-38385, you may experience issues connecting to your Electrum or C-Lightning interface.

It's easy to fix since openSUSE already has the package for latest stable release 0.4.7.8 ready and will install it by just doing a quick zypper update!

This will get you right back on track.

Code:

sudo zypper update

[n0nce]

Changelog:

29.11.2021: Update guide for electrs 0.9.3 and c-lightning 0.10.2
30.01.2022: Add RTL install instructions
17.07.2022: Update guide -- all latest versions! Bitcoin Core v23.0, electrs 0.9.8, c-lightning 0.11.2 and RTL v0.12.3.

Little bump for this guide. It's now all up-to-date again, with the latest version of every single piece of software.
I did walk through it in a VM, but can't start up most programs since they require Bitcoin Core to be up and running and fully synced, for which I don't have the space in the VM. But if someone's got a problem, I'll install it pruned, and debug it of course..

[n0nce]

Changelog:

29.11.2021: Update guide for electrs 0.9.3 and c-lightning 0.10.2
30.01.2022: Add RTL install instructions
17.07.2022: Update guide -- all latest versions! Bitcoin Core v23.0, electrs 0.9.8, c-lightning 0.11.2 and RTL v0.12.3.
22.08.2022: Update guide -- all latest versions! Bitcoin Core v23.0, electrs 0.9.9, Core Lightning v0.11.2 and RTL v0.13.0.

Updated again! Pretty excited about this one, since RTL v0.13.0 now has a pretty cool GUI for creating and finding Liquidity Ads.

[BlackHatCoiner]

I'm trying to upgrade from v0.10.2 to v0.11.2, and there must be something wrong with either my machine or this installation. I have renamed my previous lightning directory to lightning2, and I'm git-ing the new version. I do the git checkout, run the ./configure, make with make -j $(nproc), add the safe directories (lightning & lightning/external/libwally-core), but once I run sudo make install, this happens:

Code:

[...]
cc plugins/spender/openchannel.c
ld plugins/spenderp
cargo build --quiet --bin cln-grpc
error: failed to parse manifest at `/home/bitcoin/lightning/cln-rpc/Cargo.toml`

Caused by:
  failed to parse the `edition` key

Caused by:
  this version of Cargo is older than the `2021` edition, and only supports `2015` and `2018` editions.
make: *** [plugins/Makefile:194: target/debug/cln-grpc] Error 101
rm external/arm-linux-gnueabihf/libwally-core-build/src/secp256k1/libsecp256k1.la

Should I open a Github issue, or has it happened to you before, and you know how it can be resolved?

[vv181]

Code:

Caused by:
  failed to parse the `edition` key

Caused by:
  this version of Cargo is older than the `2021` edition, and only supports `2015` and `2018` editions.
make: *** [plugins/Makefile:194: target/debug/cln-grpc] Error 101
rm external/arm-linux-gnueabihf/libwally-core-build/src/secp256k1/libsecp256k1.la

What is your Cargo version?

Code:

cargo --version

[BlackHatCoiner]

What is your Cargo version?

Code:

cargo 1.48.0 (65cbdd2dc 2020-10-14)

[vv181]

What is your Cargo version?

Code:

cargo 1.48.0 (65cbdd2dc 2020-10-14)

Yea it's the older unsupported version.

It's weird because CLN plugin didn't update its Rust edition since 0.10.2. How did you install Rust and Cargo?

For the issue, simply upgrading the cargo version should suffice. You either update it from the package manager(if your package repository has min cargo v 1.56.0) or simply change/use the Rust installation method using Rustup

https://www.rust-lang.org/tools/install

Code:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

[BlackHatCoiner]

It's weird because CLN plugin didn't update its Rust edition since 0.10.2. How did you install Rust and Cargo?

I honestly don't remember installing neither of them.

Code:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

Is this supposed to change my cargo or rust version? Because I just executed it, and I'm still with the same error during sudo make install. My cargo version hasn't changed, so it was probably for rust. I don't know neither of the two, but isn't the error essentially saying that I have to upgrade my cargo?

[n0nce]

It's weird because CLN plugin didn't update its Rust edition since 0.10.2. How did you install Rust and Cargo?

I honestly don't remember install neither of them.

Do you run OpenSUSE & installed through this guide? If so, this command did it:

[1] Install dependencies, make sure you're logged into your sudoer account and not in bitcoin.

Code:

sudo zypper install clang cargo rust tor libstdc++6-devel-gcc11

I don't know neither of the two, but isn't the error essentially saying that I have to upgrade my cargo?

The error is saying that your cargo is outdated, yes.

Leap 15.3 should be giving you Rust 1.62 and accompanying cargo version.
https://software.opensuse.org/package/rust

[BlackHatCoiner]

Do you run OpenSUSE & installed through this guide?

Oh no, I used Raspibolt's guide. I presume I just need to run the same command with sudo apt install, instead?

[vv181]

Do you run OpenSUSE & installed through this guide?

Oh no, I used Raspibolt's guide. I presume I just need to run the same command with sudo apt install, instead?

That is correct but the default Debian Cargo package uses the old version.
https://tracker.debian.org/pkg/cargo

Is this supposed to change my cargo or rust version? Because I just executed it, and I'm still with the same error during sudo make install.

It supposes to change both since it comes prepackaged.

That installation should have automatically updated your PATH environment, have you tried to restart your console?

If it still does not work, updating it should do it. export PATH="$HOME/.cargo/bin:$PATH"

[BlackHatCoiner]

That installation should have automatically updated your PATH environment, have you tried to restart your console?

Yes, it's updated:

Code:

bitcoin@raspibolt:~/lightning $ cargo --version
cargo 1.63.0 (fd9c4297c 2022-07-01)

But it now fails to run custom command with this "prost-build v0.8.0":

Code:

make: *** [plugins/Makefile:191: target/debug/examples/cln-plugin-startup] Error 101
make: *** Waiting for unfinished jobs....
error: failed to run custom build command for `prost-build v0.8.0`

Caused by:
  process didn't exit successfully: `/home/bitcoin/lightning/target/debug/build/prost-build-02336ebf13cd8614/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at 'Failed to find the protoc binary. The PROTOC environment variable is not set, there is no bundled protoc for this platform, and protoc is not in the PATH', /home/bitcoin/.cargo/registry/src/github.com-1285ae84e5963aae/prost-build-0.8.0/build.rs:105:10
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
make: *** [plugins/Makefile:194: target/debug/cln-grpc] Error 101
rm external/arm-linux-gnueabihf/libwally-core-build/src/secp256k1/libsecp256k1.la

It must have to do with cargo, as it searches the .cargo path. The above is prompt on make.

I'm trying to install libprotobuf-dev, protobuf-compiler as said in Github, and I'll let you know.

Edit: Ugh, another ugly error.

Code:

error: failed to run custom build command for `cln-grpc v0.0.1 (/home/bitcoin/lightning/cln-grpc)`

Caused by:
  process didn't exit successfully: `/home/bitcoin/lightning/target/debug/build/cln-grpc-beb9091097bb64ac/build-script-build` (exit status: 101)

Followed by an endless list of stuff like:

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "protoc failed: node.proto:75:18: Explicit 'optional' labels are disallowed in the Proto3 syntax. To define 'optional' fields in Proto3, simply remove the 'optional' label, as fields are 'optional' by default.\nnode.proto:76:18: Explicit 'optional' labels are disallowed in the Proto3 syntax. To define 'optional' fields in Proto3, simply remove the 'optional' label, as fields are 'optional' by default.\nnode.proto:98:18: Explicit 'optional' labels are disallowed in the Proto3 syntax.

[n0nce]

I'm trying to install libprotobuf-dev, protobuf-compiler as said in Github, and I'll let you know.

Edit: Ugh, another ugly error.

Code:

error: failed to run custom build command for `cln-grpc v0.0.1 (/home/bitcoin/lightning/cln-grpc)`

Caused by:
  process didn't exit successfully: `/home/bitcoin/lightning/target/debug/build/cln-grpc-beb9091097bb64ac/build-script-build` (exit status: 101)

Followed by an endless list of stuff like:

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "protoc failed: node.proto:75:18: Explicit 'optional' labels are disallowed in the Proto3 syntax. To define 'optional' fields in Proto3, simply remove the 'optional' label, as fields are 'optional' by default.\nnode.proto:76:18: Explicit 'optional' labels are disallowed in the Proto3 syntax. To define 'optional' fields in Proto3, simply remove the 'optional' label, as fields are 'optional' by default.\nnode.proto:98:18: Explicit 'optional' labels are disallowed in the Proto3 syntax.

Something's off with your protobuf.

What does your machine spit out for these 2 commands?

Code:

protoc --version

locate libprotobuf

[BlackHatCoiner]

Code:

protoc --version

Code:

bitcoin@raspibolt:~ $ protoc --version
libprotoc 3.6.1

Code:

locate libprotobuf

The locate command is not found.

[n0nce]

~

Seems like an outdated version.

Make sure to update your package manager and other packages.

Code:

root$ sudo apt update && sudo apt upgrade

Then install latest protobuf using sudo apt install protobuf-compiler. On current Ubuntu it should be 3.12 or 3.14, meanwhile you've somehow got 3.6

Code:

root$ protoc --version
Command 'protoc' not found, but can be installed with:
snap install protobuf           # version 3.14.0, or
apt  install protobuf-compiler  # version 3.12.4-1ubuntu7
See 'snap info protobuf' for additional versions.

root$ sudo apt install protobuf-compiler
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  fontconfig-config fonts-dejavu-core libc-dev-bin libc-devtools libc6-dev libcrypt-dev libdeflate0 libfontconfig1 libgd3 libjbig0 libjpeg-turbo8 libjpeg8 libnsl-dev
  libprotobuf-dev libprotobuf-lite23 libprotobuf23 libprotoc23 libtiff5 libtirpc-dev libwebp7 libxpm4 linux-libc-dev manpages-dev rpcsvc-proto zlib1g zlib1g-dev
Suggested packages:
  glibc-doc libgd-tools protobuf-mode-el
The following NEW packages will be installed:
  fontconfig-config fonts-dejavu-core libc-dev-bin libc-devtools libc6-dev libcrypt-dev libdeflate0 libfontconfig1 libgd3 libjbig0 libjpeg-turbo8 libjpeg8 libnsl-dev
  libprotobuf-dev libprotobuf-lite23 libprotobuf23 libprotoc23 libtiff5 libtirpc-dev libwebp7 libxpm4 linux-libc-dev manpages-dev protobuf-compiler rpcsvc-proto
  zlib1g-dev
The following packages will be upgraded:
  zlib1g
1 upgraded, 26 newly installed, 0 to remove and 2 not upgraded.
Need to get 3888 kB/11.6 MB of archives.
After this operation, 50.4 MB of additional disk space will be used.
Do you want to continue? [Y/n]

[...]

root$ protoc --version
libprotoc 3.12.4

The following is also helpful to see what is installed and where.

Code:

root$ sudo apt install plocate
[...]

root$ locate libprotobuf
/snap/lxd/22923/lib/x86_64-linux-gnu/libprotobuf-c.so.1
/snap/lxd/22923/lib/x86_64-linux-gnu/libprotobuf-c.so.1.0.0
/usr/lib/x86_64-linux-gnu/libprotobuf-lite.a
/usr/lib/x86_64-linux-gnu/libprotobuf-lite.so
/usr/lib/x86_64-linux-gnu/libprotobuf-lite.so.23
/usr/lib/x86_64-linux-gnu/libprotobuf-lite.so.23.0.4
/usr/lib/x86_64-linux-gnu/libprotobuf.a
/usr/lib/x86_64-linux-gnu/libprotobuf.so
/usr/lib/x86_64-linux-gnu/libprotobuf.so.23
/usr/lib/x86_64-linux-gnu/libprotobuf.so.23.0.4
/usr/share/doc/libprotobuf-dev
/usr/share/doc/libprotobuf-lite23
/usr/share/doc/libprotobuf23
/usr/share/doc/libprotobuf-lite23/changelog.Debian.gz
/usr/share/doc/libprotobuf-lite23/copyright
/usr/share/doc/libprotobuf23/changelog.Debian.gz
/usr/share/doc/libprotobuf23/copyright
/var/cache/apt/archives/libprotobuf-dev_3.12.4-1ubuntu7_amd64.deb
/var/cache/apt/archives/libprotobuf-lite23_3.12.4-1ubuntu7_amd64.deb
/var/cache/apt/archives/libprotobuf23_3.12.4-1ubuntu7_amd64.deb
/var/lib/dpkg/info/libprotobuf-dev:amd64.list
/var/lib/dpkg/info/libprotobuf-dev:amd64.md5sums
/var/lib/dpkg/info/libprotobuf-lite23:amd64.list
/var/lib/dpkg/info/libprotobuf-lite23:amd64.md5sums
/var/lib/dpkg/info/libprotobuf-lite23:amd64.shlibs
/var/lib/dpkg/info/libprotobuf-lite23:amd64.triggers
/var/lib/dpkg/info/libprotobuf23:amd64.list
/var/lib/dpkg/info/libprotobuf23:amd64.md5sums
/var/lib/dpkg/info/libprotobuf23:amd64.shlibs
/var/lib/dpkg/info/libprotobuf23:amd64.triggers