It’s just a much better terminal than the default one that ships with Windows. Not necessary, but just so much better to use.
It’s a Microsoft product, so it’s developed in house and a very good product. Very professionally done.
Here’s a couple of examples from my own Windows PC:
Thanks for the tip, I’ll definitely do that, and for now I wll post the screenshots after each command.
Thanks. Although you’ve not actually ran the safeup --version command there.
So what should I do?
You’ve ran the command that installs safeup. What I’d like to see is you running this command:
safeup --version
Hmm, I don’t really understand why you aren’t getting any output there. I’m not sure that the safeup binary is actually running.
There might be something funny going on with your shell setup. What is the output of this command?
$env:Path
Edit: Actually, I’m only really interested in the value of the Path variable.
I typed the commands as in your screenshots, after typing
safeup --version
safeup 0.3.6
no response
After typing the command
safeup client -v 0.79.5
no response
And then I typed the value
Path
Yeah, you’re just not getting any output from the safeup binary there. I don’t think it’s actually running, but I don’t know why.
You need to use $env:Path, not just Path.
Updates:
CHUNK_DELETEDrecord_store folder in the first half off the node’s lifespan, even after hitting 2048 max record entriesObservations:
safenode pid in terms of auto-incrementing #s etc. This would make it more difficult to triage or trace something if #s are overlapping in a small time span possibly, unless off-course this is all part of a single request chain, in that case it took 66000 seconds to finish, which I don’t think is the case here. Or, the id originated from external node for the first batch, and at same time, the same # was originated as part off a new request later on within the current safenode. 
[2023-07-09T13:26:35.513186Z TRACE sn_networking::msg] Received request with id: RequestId(73737), req: Cmd(RequestReplication(NetworkAddress::PeerId([0, 36, 8, 1, 18, 32, 97, 141, 115, 255, 181, 244, 206, 81, 142, 146, 231, 153, 104, 10, 213, 212, 241, 10, 163, 2, 198, 13, 195, 190, 63, 153, 71, 255, 59, 67, 8, 71])))
[2023-07-09T13:26:35.666447Z TRACE sn_networking::msg] ResponseSent for request_id: RequestId(73737) and peer: PeerId("12D3KooWGPApMpUPuyjxo2Qzz2kKy2SLgrhtZ7k2sdBFQ7aujH82")
...
[2023-07-10T07:47:40.049038Z TRACE sn_networking::cmd] Sending request RequestId(73737) to peer PeerId("12D3KooWGXuo2vzYHWwbwHg45BuLstegGcyHHyWEzruSQYqRUN6x")
[2023-07-10T07:47:40.722538Z TRACE sn_networking::msg] Got response for id: RequestId(73737), res: Cmd(Replicate(Ok(()))).
VALIDATE_AND_STORE_CHUNK (53454) → STORING_CHUNK (53448) → VALIDATED_AND_STORED (53332) → CHUNK_WRITTEN (48538). Should some of these have been exactly equal #s?
There were some immediate failures associated with no such file or directory following a PUT verified record entry (291 times). Is that expected?:
[2023-07-09T02:05:55.981021Z TRACE sn_networking::msg] Got response for id: RequestId(172), res: Query(GetReplicatedData(Ok((NetworkAddress::PeerId([0, 36, 8, 1, 18, 32, 9, 200, 155, 91, 60, 252, 64, 90, 20, 62, 248, 218, 201, 14, 128, 12, 150, 40, 221, 152, 168, 38, 15, 29, 138, 78, 224, 3, 225, 173, 57, 105]), Chunk(ChunkWithPayment { chunk: Chunk { address: ChunkAddress(004193(00000000)..) }, payment: None }))))).
[2023-07-09T02:05:55.981150Z TRACE sn_node::api] NetworkEvent::ResponseReceived Query(GetReplicatedData(Ok((NetworkAddress::PeerId([0, 36, 8, 1, 18, 32, 9, 200, 155, 91, 60, 252, 64, 90, 20, 62, 248, 218, 201, 14, 128, 12, 150, 40, 221, 152, 168, 38, 15, 29, 138, 78, 224, 3, 225, 173, 57, 105]), Chunk(ChunkWithPayment { chunk: Chunk { address: ChunkAddress(004193(00000000)..) }, payment: None })))))
[2023-07-09T02:05:55.981180Z DEBUG sn_node::api] Chunk received for replication: 004193(00000000)..
[2023-07-09T02:05:55.981190Z DEBUG sn_node::put_validation] validating and storing chunk 004193(00000000)..
[2023-07-09T02:05:55.981243Z DEBUG sn_node::put_validation] Storing chunk 004193(00000000).. as Record locally
[2023-07-09T02:05:55.981258Z DEBUG sn_networking] Writing Record locally, for Key(b"\0A\x93\x06\x85\xa7x\x8au\xc3\xf59\xb3\x8a\x13\xaf\xca\xeaU\xf0\x95\x90 \xd7J\xf1\xfdO\x88\xc7\x150") - length 2055
[2023-07-09T02:05:55.981288Z TRACE sn_node::api] ReplicatedData::Chunk with ChunkAddress(004193(00000000)..) has been validated and stored. StoredSuccessfully
[2023-07-09T02:05:55.981319Z TRACE sn_networking::record_store] PUT a verified Record: Key(b"\0A\x93\x06\x85\xa7x\x8au\xc3\xf59\xb3\x8a\x13\xaf\xca\xeaU\xf0\x95\x90 \xd7J\xf1\xfdO\x88\xc7\x150")
[2023-07-09T02:05:55.981405Z ERROR sn_networking::record_store] Error writing file. filename: 0041930685a7788a75c3f539b38a13afcaea55f0959020d74af1fd4f88c71530, error: Os { code: 2, kind: NotFound, message: "No such file or directory" }
Note: Will dig in further in a few hours from now, but the above was a first pass on my current safenode logs.
Since you wrote in the edit that you were only interested in the Path value, I understood that I should omit $env:
So now I typed the whole command: $env:Path
Hmm, I’m genuinely not sure what is going on with your setup, sorry. I think there are issues here beyond safe related things.
Honestly, I’m not sure, but you should see some output from the safeup binary when you run it.
The safe client currently is not on your system. The safeup client -v 0.79.5 command is supposed to retrieve the binary for you.
I see, thank you for your help, I will try again as I wrote.
I will delete unnecessary posts as I do not want to clutter the thread.
If your node has moved, or there’s been churn it doesnt attempt to clean up until it needs space. So that’s likely what you’re seeing here @anon26713768
@Profess the export example is for ubuntu, you’ll need the windows setup in the OP.
An alternative is to simply pass the --peer arg instead of trying to set an env var.
It’s not just setting the peer variable, there’s something else going on with his setup. The safeup binary doesn’t even appear to run in the shell.
I have managed to resolve the issue.
I tried running the commands in different Win PowerShell options and only after running PowerShell ISE as Administrator and typing the command:
safeup --version
command displays the message:
safeup.exe - system error - due to missing VCRUNTIME140.dll file After installing the file from the Windows website, the commands started to respond.
However, after entering the command according to your instructions
That is, instead of “export” I typed “$env:” this message appeared:
you didnt upload anything, thats just the example command line. you need / could upload a file. thats what it complains about. specify a real filename (pathname with filename) instead of the < path > you left there from the example command line
That is because you have to type a path to the file you want to upload instead <path> fragment.
Hmm, it looks like you’ve got some kind of strange kind of setup going on with this computer.
None of the safe-related binaries require admin access.
As others have pointed out, you need to replace that <path> placeholder with a real file, but also, setting the SAFE_PEERS environment variable should be its own command, so that it will persist for the remaining safe commands for that shell session.
