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?
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 . .
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
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
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.