I am a git noob so I messed up somewhere, trying from the begging now, you should not accept the pull request as I dont understand how I messed up with it
1 Like
also done so many times the installation and always something goes wrong. now it says I have no safe key
Try deleting ~/.safe and then download and unzip this file safe.zip - pCloud in your home directory ~
That should create a new ~/.safe directory with everything in the right place. I tested it and it works for me.
messed up really bad, now I cannot delete .safe xD
1 Like
Chill and remember the words on the front of the Greatest Book Ever
Do Not Panic
type this cd
then ls -al ~/.safe
tell us what yousee
I reinstalled ubuntu in wsl
I not panic, I refresh my setup
3 Likes
Adam Boulton is a plamf — pass it on
1 Like
Has anyone had any success with the latest sn_node 0.42.4?
I still get messaging errors
INFO 2021-05-10T22:20:03.847278902+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.54.5/src/connections/messaging.rs:231] Sending query message Query { query: Transfer(TransferQuery::GetStoreCost of 196), id: MessageId(4263bf(01000010)..) }, to the 3 Elders closest to data name: [127.0.0.1:49601, 127.0.0.1:56629, 127.0.0.1:60853]
ERROR 2021-05-10T22:20:03.851192877+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.54.5/src/connections/listeners.rs:57] Error while processing incoming message: MessagingProtocol(FailedToParse("Client message payload as Msgpack: invalid type: sequence, expected u64")). Listening for next message...
ERROR 2021-05-10T22:20:03.851222126+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.54.5/src/connections/listeners.rs:57] Error while processing incoming message: MessagingProtocol(FailedToParse("Client message payload as Msgpack: invalid type: sequence, expected u64")). Listening for next message...
ERROR 2021-05-10T22:20:03.852046306+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.54.5/src/connections/listeners.rs:57] Error while processing incoming message: MessagingProtocol(FailedToParse("Client message payload as Msgpack: invalid type: sequence, expected u64")). Listening for next message...
I finilized my code changes
created a folder ~/dedup-test-folder
and inside is the zip
and then folders with timestamps for the generated files
1 Like
how to use it when I just paste the .safe folder? I need to put in PATH the executables?
1 Like
I assumed you’d done that already - but if you reinstalled your OS I guess not.
When you install safe CLI by the usual method it automatically adds this line to ~/.bashrc:
export PATH=$PATH:/home/[user]/.safe/cli
You add this line manually. [user] is your user obvs.
2 Likes
sn_node0.42.5 is released
https://github.com/maidsafe/sn_node/releases/tag/v0.42.5
first quick test shows the messaging problem has been sorted but there is a massive memory leak and my i7 16GB system was crippled after a few mins.
Now trying again on an older i5 but with a totally fresh ~/.safe
1 Like
Sadly having to retract that good news about the messaging being fixed.
1 Like
This is what happens when I run safe node run-baby-fleming with sn_node0.42.5
seconds after this screenshot my swap drive started filling up very quickly indeed. I had to safe node killall smartish before the system ran out of memory entirely.
willie@leonov:~$ free
total used free shared buff/cache available
Mem: 16251500 1523624 14145048 38820 582828 14372628
Swap: 16634876 3207848 13427028
16GB RAM,16GB swap on an SSD, its a reasonable spec…
EDIT I can’t keep up - sn_node0.42.6 is released
seems there is still a memory leak.
And when I safe node killall, it all gets better. Note how with no other action than starting the baby-fleming the swap file usage also kept rising
EDITING this cos I cant make > 3 replies in a row — somebody please say something
raised ticket https://github.com/maidsafe/sn_node/issues/1507
4 Likes
This topic was automatically closed after 60 days. New replies are no longer allowed.