Podman: Void Linux + runit (ie NO systemd) VM + safenode

People,

I haven’t been able to get my CLI script on Fedora 40 using safenode-manager to get past just talking to peers - but node-launchpad works so I have just left that running for now.

However, I have been interested in running other things inc VMs and when I also became interested in using runit instead of systemd, I decided to give that a shot.

So now I have a singe node running - showing lots of INFOs WARNs and ERRORs in the log - but without node-launchpad, how do I work out if the node is doing anything useful?

Thanks,
Phil.

When using launchpad, what connection options do you select?

On the Void Linux VM? - LP doesn’t run on non-systemd systems . .

You said this, and I asked what connection options are you using?

Also I run nodes without runit or systemd, just run then in a terminal with safenode

I meant it worked on the Fedora 40 (systemd) non-VM setup - I am not worried about that - the Q was about the VM setup . .

OK, that is what I am doing on the VM - my Q was how can I see what the node(s) is(are) doing in some summarised way? - does someone have scripts that will process the logs or something? - since I can’t use LP . .

If runit and systemd are not working for you then

safenode --home-network --rewards-address 0x…eth.addr… evm-arbitrum-sepolia &

This puts the safenode into the background. If you logout or kill the terminal then it causes the node to stop ← warning. Use screen or similar to run the terminal in so that it survives logging out

vdash can be used to monitor the nodes

Yes, I wasn’t concerned about that - I can run as many tmux terms etc that I want . .

Ah - OK, I will check that out . . thanks!

No need to have multiple terms, just put the nodes into the background with “&”, so only one terminal needed, and that terminal can run vdash after starting the nodes

Sure - what I meant was that I know that - that wasn’t the Q . .

Thanks.

1 Like

Stuck on building vdash on this setup - I will send @happybeing a note - but has he time to look at the debug output?

If you provide details we can see!

First though:

rustup update
cargo install vdash
1 Like

Messaged long output - have now switched from pkg rust to rustup and redone “cargo install vdash” - the end of the output is different now:

  = note: cc: fatal error: '-fuse-linker-plugin', but liblto_plugin.so not found
          compilation terminated.
          

error: could not compile `proc-macro2` (build script) due to 1 previous error
error: could not compile `libc` (build script) due to 1 previous error
error: failed to compile `vdash v0.18.1`, intermediate artifacts can be found at `/tmp/cargo-installq0Ggk1`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

I’m afraid you will need to try some web searches for that first error and see where it goes. I’ve not seen that before so you may be missing some dependencies for the particular distro.

1 Like

make sure you have build-essential installed.

1 Like

@Southside , on Void Linux it is “base-devel” but after installing that I still get the same error as above unfortunately . .

I will be away for a couple of days now and will look at this again when I get back . .

Thanks!

2 Likes

This topic was automatically closed after 59 days. New replies are no longer allowed.