Launchpad headless? Aye atm, there’s nothing there, it’s just a wrapper for nodemanager
anyway. Proobably later the TUI might get merged together with nodeman, but we’ll see!
Nah no need, I thought you may be pushing launchpad because it calculates nodes for you. Just in case I already had my own custom version
I tried safe launcher on windows was painless after exluding it from Nortons wrath.
the network I am on blocks udp so I could not start the nodes on windows ill test tomorrow when I am at another location for internet access.
for my normal set up I added the nodes with safenode-manager and having the --owner flag set for the discord username and rewards are coming in but unfortunately the seem to be flowing back out.
is this part of the plan ?
the graph is generated from the rewards balance displayed by
safenode-manager status --details
@joshuef Will we/do we have to just the discord ID here. Or is it just optional so the rewards earned can be displayed here in the topic
I would like to be able to track my rewards myself without relying on the leaderboard.
I guess Vdash is a option as it records the logs but there are discrepancies there, or there were. perhaps we can get a script going for ntracking to log rewards before they take off to the foundation.
perhaps we can do it like vdash does it and get the rewards from the logs ?
Been a long day, let’s figure it out tomorrow. I don’t want to look at screens anymore
I didn’t mean right now lol
or if this is how its meant to be perhaps an additional log file rewards.log
could be written alongside safenode.log
?
what do you thing @joshuef
yeah but they appear to be forwarded out of ther to the foundation. so it needs a record of sorts. that’s what appears to be happening.
edit… @neo you cant ninja me like that
hahaha #metoo
Thats why my ninja. I realised i was so wrong hoping you wouldn’t have read it by then
What prevents people from sending faucet tokens to node wallets that then get forwarded to the foundation to be tallied as legitimate rewards?
Other than being called out and making a ass out of yourself?
4GB kali linux uploaded
large uploads seem to run fine stop for a while and resume any one else seeing this behaviour ?
— edit
perhaps batch size 200 was a bit ambitious 64 is working much smother
"kali-linux-2023.3-installer-amd64.iso" b6eea5ffd85a1dfe5b2804c4a50e04f317676e47ef89cfd19d8c074ea1baba65
"CentOS-7-x86_64-DVD-2009.iso" 1c9e8596f71fc6b162fa0e46c97f380bad6d8b6e5fe9876a74a7aa73fc06399f
hahaaaa - very cool - i just figured out how to do a clean reset of my whole system missed the community net - but seems more or less on time for this one!
discord username: rid._.dim
just added some nodes (0.106.5) with the additional --owner +discord-name
(i know it’s about the TUI … but thought it would be nice to see if the terminal stuff works in combination with the owner)
EDIT:
damn … i’m seeing rewards … i guess that means something is wrong … -.-" …
oh - i see - rewards appear and vanish again
EDIT2:
hahaa - now since i scrolled back and was looking if there is a link to the board i saw your screenshot @aatonnomicc - looks not thaaat different xD …
maybe that translates badly
Come on in any way
discord username: southside
20 nodes started so far
212 matches on 'Dcutr with remote peer: PeerId\("\w+"\) is: Err'
willie@gagarin:~/.local/share/safe/node$ rg 'Dcutr with remote peer: PeerId\("\w+"\) is: Err' --search-zip --count --stats
safenode7/logs/safenode.log:10
safenode18/logs/safenode.log:12
safenode20/logs/safenode.log:9
safenode15/logs/safenode.log:6
safenode4/logs/safenode.log:12
safenode9/logs/safenode.log:18
safenode2/logs/safenode.log:13
safenode19/logs/safenode.log:7
safenode5/logs/safenode.log:14
safenode13/logs/safenode.log:5
safenode1/logs/safenode.log:21
safenode3/logs/safenode.log:14
safenode16/logs/safenode.log:11
safenode10/logs/safenode.log:14
safenode12/logs/safenode.log:1
safenode8/logs/safenode.log:12
safenode14/logs/safenode.log:10
safenode17/logs/safenode.log:5
safenode6/logs/safenode.log:12
safenode11/logs/safenode.log:6
212 matches
212 matched lines
20 files contained matches
7178 files searched
0 bytes printed
88169184 bytes searched
0.164504 seconds spent searching
0.028473 seconds
dont care that I am losing rewards it looks awesome
oh right … not sure it’s of interest for cloud nodes … since it’s about home node issues (not sure they appear in the cloud log files (?) but maidsafe probably wouldn’t need us then … since they run a lot of cloud instances anway …)
anyway … here we go so far - only single digit results for nodes … most between 1 and 3 so far …
ripgrep
host:
safenode10/safenode.log:1
safenode9/safenode.log:2
safenode4/safenode.log:1
safenode8/safenode.log:3
safenode13/safenode.log:4
safenode5/safenode.log:1
safenode7/safenode.log:1
13 matches
13 matched lines
7 files contained matches
30 files searched
0 bytes printed
42400378 bytes searched
0.018710 seconds spent searching
0.009848 seconds
host:
safenode13/safenode.log:1
safenode7/safenode.log:4
safenode4/safenode.log:1
safenode3/safenode.log:1
safenode10/safenode.log:3
safenode14/safenode.log:1
safenode12/safenode.log:1
safenode6/safenode.log:3
safenode2/safenode.log:3
safenode8/safenode.log:3
21 matches
21 matched lines
10 files contained matches
30 files searched
0 bytes printed
44631896 bytes searched
0.015915 seconds spent searching
0.008934 seconds
host:
safenode11/safenode.log:1
safenode1/safenode.log:1
safenode7/safenode.log:2
safenode3/safenode.log:1
safenode2/safenode.log:2
safenode6/safenode.log:3
safenode9/safenode.log:1
safenode8/safenode.log:3
safenode13/safenode.log:2
safenode5/safenode.log:7
safenode14/safenode.log:1
24 matches
24 matched lines
11 files contained matches
30 files searched
0 bytes printed
43647422 bytes searched
0.014532 seconds spent searching
0.015603 seconds
host:
safenode13/safenode.log:1
safenode7/safenode.log:4
safenode4/safenode.log:2
safenode10/safenode.log:1
safenode12/safenode.log:1
safenode6/safenode.log:3
safenode2/safenode.log:2
safenode8/safenode.log:2
safenode9/safenode.log:1
17 matches
17 matched lines
9 files contained matches
30 files searched
0 bytes printed
45258868 bytes searched
0.013635 seconds spent searching
0.009816 seconds
host:
safenode6/safenode.log:1
safenode9/safenode.log:1
safenode8/safenode.log:3
safenode4/safenode.log:1
safenode13/safenode.log:1
safenode10/safenode.log:1
safenode12/safenode.log:1
safenode5/safenode.log:6
safenode3/safenode.log:1
safenode7/safenode.log:3
19 matches
19 matched lines
10 files contained matches
30 files searched
0 bytes printed
42425554 bytes searched
0.021134 seconds spent searching
0.008871 seconds
host:
safenode4/safenode.log:2
safenode10/safenode.log:3
safenode13/safenode.log:3
safenode12/safenode.log:3
safenode8/safenode.log:1
safenode3/safenode.log:2
safenode9/safenode.log:3
safenode6/safenode.log:1
safenode2/safenode.log:1
safenode14/safenode.log:1
safenode7/safenode.log:2
22 matches
22 matched lines
11 files contained matches
30 files searched
0 bytes printed
37369492 bytes searched
0.020136 seconds spent searching
0.009522 seconds
host:
safenode6/safenode.log:1
safenode4/safenode.log:3
safenode9/safenode.log:1
safenode8/safenode.log:3
safenode10/safenode.log:1
safenode1/safenode.log:2
safenode3/safenode.log:1
safenode5/safenode.log:1
safenode7/safenode.log:2
15 matches
15 matched lines
9 files contained matches
30 files searched
0 bytes printed
39713518 bytes searched
0.023541 seconds spent searching
0.010416 seconds
host:
safenode9/safenode.log:2
safenode7/safenode.log:2
safenode14/safenode.log:1
safenode10/safenode.log:1
safenode4/safenode.log:4
safenode6/safenode.log:3
13 matches
13 matched lines
6 files contained matches
30 files searched
0 bytes printed
40363780 bytes searched
0.027582 seconds spent searching
0.011531 seconds
host:
safenode6/safenode.log:2
safenode9/safenode.log:2
safenode2/safenode.log:1
safenode13/safenode.log:1
safenode10/safenode.log:1
safenode8/safenode.log:2
safenode1/safenode.log:1
safenode12/safenode.log:1
safenode3/safenode.log:2
safenode7/safenode.log:5
18 matches
18 matched lines
10 files contained matches
30 files searched
0 bytes printed
40643144 bytes searched
0.024518 seconds spent searching
0.009729 seconds
host:
safenode9/safenode.log:1
safenode7/safenode.log:5
safenode4/safenode.log:2
safenode3/safenode.log:2
safenode10/safenode.log:2
safenode6/safenode.log:5
safenode5/safenode.log:1
safenode1/safenode.log:1
safenode13/safenode.log:2
safenode2/safenode.log:2
23 matches
23 matched lines
10 files contained matches
30 files searched
0 bytes printed
41594176 bytes searched
0.027326 seconds spent searching
0.011690 seconds
host:
safenode1/safenode.log:2
safenode4/safenode.log:1
safenode6/safenode.log:1
safenode8/safenode.log:1
safenode13/safenode.log:1
safenode10/safenode.log:3
safenode5/safenode.log:1
safenode9/safenode.log:1
safenode2/safenode.log:2
13 matches
13 matched lines
9 files contained matches
30 files searched
0 bytes printed
42916160 bytes searched
0.018106 seconds spent searching
0.010122 seconds
will bring my upnp pi as soon as i can as well and have a look there …
I can run nodes fine -earned 200+ nanos so far but I cant connect with the client at all…
willie@gagarin:~/projects/maidsafe/NTracking$ safe wallet get-faucet 161.35.173.105:8000
Logging to directory: "/home/willie/.local/share/safe/client/logs/log_2024-05-26_05-00-05"
safe client built with git version: 2a695ca / alpha-reward-test / 2a695ca / 2024-05-24
Instantiating a SAFE client...
Connecting to the network with 39 peers
🔗 Could not connect to the network Error:
0: Could not connect to the network in 30s
Location:
sn_cli/src/bin/main.rs:135
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
willie@gagarin:~/projects/maidsafe/NTracking$ safe files download "BegBlagandSteal.mp3" 3509bad03dc869dec883c7b44662c3503d2517fa9e828bb64f4dbe719d3837bf
Logging to directory: "/home/willie/.local/share/safe/client/logs/log_2024-05-26_05-02-05"
safe client built with git version: 2a695ca / alpha-reward-test / 2a695ca / 2024-05-24
Instantiating a SAFE client...
Connecting to the network with 39 peers
🔗 Could not connect to the network Error:
0: Could not connect to the network in 30s
Location:
sn_cli/src/bin/main.rs:135