Safe dog seems to work but should I have a file somewhere on my system? Safe cat still hangs. Managed to get a node running and have chunks stored 
1 Like
Once again some black holes: sections 00 and 01 (no connections possible for clients with pk beginning with 0ā¦7)
As we progress you will see change, but these can validly not respond and then recover right now. So temp back hole or permanent we need to find out. Better logging will help again. We need to see if Elders are bing swamped (we have no traffic priorities in place yet).
2 Likes
i didnāt want to grow up so I went to sea lol
13 Likes
I got connected you were right about connection.
right now I have Debian buster in virtual box on windows 10 on a ship in Azerbijan
after I connected windows 10 through a wire guard VPN back to Glasgow I manged to create keys
9 Likes
W8.2
I have some chunks but these have only 1-5KB
Edit: after few more minutes I have got few new 1MB chunks.
I can not cat any file or put own file even I have 1000 testcoins
I am patiently waiting in line, now that a new version of node has been released should everyone stop the old and start the new?
4 Likes
building the new version, not sure when I should start using it either
1 Like
Boom I AM ONLINE!!!
@happybeing thank you soooo much for your install scripts and vdash.
Once I figured out how to get rust installed properly on raspberry pi ā¦ wellā¦ take a look at this!!!
4096kb is the forum upload limit so had to re-record a very short version.
Had a longer gif but it was rejected.
recorded straight to gif using vokoscreen on pi.
resized using https://ezgif.com/
12 Likes
UPDATE FROM MAIDSAFE HQ
We have a new version of sn_node ready to go that we believe will resolve some of the issues seen this evening - we tracked down that when an Adult was being promoted to become an Elder, the network was not noting that an Adult had therefore been ālostā and so not accepting a new node to replace that Adult. This was leading to sections with few, or even zero adults, and so causing several issues.
The fix is merged and there is a new sn_node version released, but we need to restart the whole network - there isnāt much to gain in only having some of us using the new nodes.
We were looking at restarting all of the D.O. nodes live, one at a time, one every few minutes, but after talking this through it makes more sense to wipe the slate here and start again.
PLAN - Fleming Testnet v4 to restart tomorrow morning with fresh, upgraded nodes
We will let you know in this thread once a new v4 testnet is live.
We will leave the current testnet up overnight and destroy in the morning.
EDIT: if you wish to try with the new version tonight you of course can, but with so many nodes still using the old version we believe it will not solve any issues until they are all updated.
34 Likes
I guess many testers read this topic.
So it worth trying.
Even if result will bring nothing interesting.
4 Likes
Only just finished compiling on my Pi
Will the installer support Pi tomorrow?
4 Likes
ahhh man! Hang in there Zoki!
5 Likes
Iām wiping ~/.safe and starting from scratch with sn_node v0.38.5. As my concept of āmorningā is probably somewhat different from yours, Iāll just do safe node join and let it pick up chunks whenever the network starts accepting new nodes again
1 Like
cd sn_node
git checkout -f .
git pull
cargo build --release
Then copy the executable as you must have done before and off you go. Iām doing this right now for my Odroid.
@Southside I re-downloaded my cloud node and it got in right away on safe node join. Look at this and weep:
7 Likes
ya knowā¦ why not!
Doing it now.
3 Likes
so you donāt rm the files ? just replacing the node executable ?
I donāt think it matters in this case. Chunks will sit there unused. You could remove them if you prefer. I did the net setup again tho.
2 Likes