It’s possible this is a factor as I generally only run ten nodes so please make a note of this in your report - and yes that issue would be good to add to
2 Likes
The workaround is to use something like vdash $(realpath $HOME/.local/share/safe/node/*/logs/safenode.log). Works great.
Edit: To be clear, this is a workaround for vdash not following symbolic links.
1 Like
Isn’t glob scan only when you have vdash running and than in another cli you add new node than you hit r and that new node shoud be added to that vdash window? the stats are not syncing for me even with 10 or less nodes.
1 Like
Glob paths are re-scanned in a running vdash using r, and that should pick up any new nodes on the same path, although that isn’t working for some.
The README explains the intended behaviour, anything else is a bug.
1 Like
I am correctly using the -g flag and now “r” works as intended.
The problem was that if you start without the -g flag and just give the path to the log files, vdash works 99.9% as expected - kinda rewarding bad behaviour - perhaps a tweak to the usage message?
Without -g is also valid and was the old behaviour, but as you have learned is for one or more paths to a logfile, not a glob path.
I could force people to use a flag before each regular path (eg --logfile-path <PATH>) but I’m not sure about that.
I suggest that for now you update the OP for the issue to explain why ‘r’ might not work so others can find this explanation. Longer term it might be useful for vdash to show a status message if ‘r’ is pressed when ‘-g’ has not been used?
Thanks for reporting!
1 Like
Do we have a bug and hyper-inflation?
I used the SAFE_PEERS from @riddim and was able to get coins from the faucet. THen I tried an upload cos @aatonnomicc has been waiting for weeks for this buuuut…
says I have 0 nanos but safe wallet balance disagrees…
Not that it matters, NanoTokens(63556685557526773) is a bit steep no matter how much @aatonnomicc wants that boring New Order mince…
willie@gagarin:~/.local/share/safe/node$ safe files upload -p -b32 ~/Music/New\ Order/
Logging to directory: "/home/willie/.local/share/safe/client/logs/log_2024-05-26_13-34-33"
Built with git version: 04100a2 / alpha / 04100a2 / 2024-04-17
Instantiating a SAFE client...
Trying to fetch the bootstrap peers from https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
Connecting to the network with 49 peers
🔗 Connected to the Network Chunking 68 files...
"/home/willie/Music/New Order/" will be made public and linkable
Splitting and uploading "/home/willie/Music/New Order/" into 1614 chunks
Error:
0: Not enough balance in wallet to pay for chunk. We have NanoTokens(0) but need NanoTokens(63556685557526773) to pay for the chunk
Location:
/home/runner/work/safe_network/safe_network/sn_cli/src/files/files_uploader.rs:166
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
willie@gagarin:~/.local/share/safe/node$ safe wallet balance
Logging to directory: "/home/willie/.local/share/safe/client/logs/log_2024-05-26_13-35-06"
Built with git version: 04100a2 / alpha / 04100a2 / 2024-04-17
2.000000000
wrong thread - sorry
1 Like
Can I have some help with this lovely piece of code. Under Ubuntu 22.04 when I run the command “sudo apt-get install build-essential” it asks me for the Ubuntu CDrom.
I add it like this “sudo mkdir -p /cdrom” and then “sudo mount -o loop /home/dimitar/Downloads/ubuntu-22.04.4-desktop-amd64.iso /cdrom” but again I get here:
Privacy. Security. Freedom
For me worked this way (make sure that you have all packages updated):
curl --proto '=https' --tlsv1.3 https://sh.rustup.rs -sSf | sh
source $HOME/.cargo/env
sudo apt install build-essential
cargo install vdash
sudo /root/.cargo/bin/vdash --glob-path /var/log/safenode/**/safenode.log
4 Likes
A minor update to vdash is available on crates.io, install/update using:
cargo install vdash
If you don’t yet have Rust you’ll need that first. More on this and everything else are in the README.
What’s New in v0.17.8
Two PRs from a helpful community member 
:
- speed up loading of existing logfiles
- fix to checkpoints feature ensuring accuracy of stats after re-start of
vdash
Display Earnings in Fiat (£/$ etc)
Don’t forget that you can configure vdash to display not just using nanos but your chosen currency. See Vdash - dashboard for Autonomi nodes - #188 by happybeing
24,000 downloads
According to crates.io, vdash has already been downloaded 24,912 times! 
11 Likes
I got some error.
master@master-pc:~/.local/share/safe/node/safenode10/logs$ cargo install update
Updating crates.io index
Downloaded update v0.0.0
Downloaded 1 crate (940 B) in 3.11s
error: there is nothing to install in update v0.0.0, because it has no binaries
cargo install is only for installing programs, and can’t be used with libraries.
To use a library crate, add it as a dependency to a Cargo project with cargo add.
, try:
3 Likes
I’m trying to install vdash but so far no success, having this error:
error: linker
ccnot found
|
= note: No such file or directory (os error 2)error: could not compile
proc-macro2(build script) due to 1 previous error
error: failed to compilevdash v0.17.8, intermediate artifacts can be found at/tmp/cargo-installg8iOyW.
To reuse those artifacts with a future compilation, set the environment variableCARGO_TARGET_DIRto that path.
any idea how to fix it? thank you
Yes, follow the tutorial about installing rust. You have a special paragraph about the issue there.
Hmm,… node manager reports 140 nanos, Discord 130 and Vdash 258. I guess the discord bot is just coming a little behind, but why does Vdash show so much more?
I think I saw something related to this just a moment ago somewhere here in the forum, but cannot find it now.
1 Like
I’m trying out Vdash on a VPS I’m running, and lots of the nodes say INACTIVE (X mins).
If this is happening a lot, does it tend to mean there’s an issue with my setup, e.g. not enough CPU vs node load, or bandwidth etc?
The setup uses spinning hard drives vs SSDs. I’ve definitely got enough storage and RAM for the nodes, and CPU should be sufficient. Any help would be appreciated!
2 Likes
Did you start vdash soon after the nodes or much later?
If soon after, this may mean they aren’t connecting for some reason. Look at the logs.
INACTIVE just means they have not written to the logs for more than 20s
2 Likes
Thanks for the input. I started vdash soon after the nodes, and it was fine for a good number of hours, then INACTIVE started to appear more & more frequently, with the time growing from flashing on & off, to 10s of minutes, until I (perhaps wrongly!) assumed many nodes were dying.
I thought I’d try a reboot, but now safenode-manager gets stuck on ‘refreshing the node registry’ & won’t do anything else.
I’ll have a prod further and see if I can see anything fishy.
1 Like
This helped… CPU was sitting at 99%! So it seems that is the culprit - overloaded CPU.
Sometimes individual nodes were using 10% of CPU, and regularly 2-3%. It’s an i7-7700, and I was running 200 nodes on it… perhaps it’s a bit much for it!
3 Likes