Are you referring to the code of that “successrate” programme or the symbol I used to highlight the screenshot?
The symbol to mark the code block is called “backtick”. One such symbol can outline the one line of the code, three such symbols the multiline code block
1 Like
Okay, Got it
So whenever I want to share a screenshot of my PowerShell, I have to use three of those symbol. Am I right?
Three before the block and three after the block
1 Like
Here is a screenshot of my desktop.
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell https://aka.ms/pscore6
PS C:\Users\dhiwa\Downloads\success_rate-master\success_rate-master> Unblock-File C:\Users\dhiwa\Downloads\success_rate-master\success_rate-master\successrate.ps1
PS C:\Users\dhiwa\Downloads\success_rate-master\success_rate-master> ./successrate.ps1 -Path "$env:ProgramFiles/Storj/Storage Node/storagenode.log"
========== AUDIT =============
Successful: 75
Recoverable failed: 0
Unrecoverable failed: 0
Success Min: 100%
Success Max: 100%
========== DOWNLOAD ==========
Successful: 2450
Failed: 72
Success Rate: 97.1451229183188
========== UPLOAD ============
Successful: 39235
Rejected: 0
Failed: 135
Acceptance Rate: 100
Success Rate: 99.6570993141986
========== REPAIR DOWNLOAD ===
Successful: 0
Failed: 0
Success Rate: 0
========== REPAIR UPLOAD =====
Successful: 235
Failed: 0
Success Rate: 100
PS C:\Users\dhiwa\Downloads\success_rate-master\success_rate-master>
Please make me understand what does sucess rate in download and upload mean?
It looks like you’re still using the old version of the script, you should download the new one from the link in the top post. The success rate tells you what percentage of transfers completes successfully. Failed means there was some sort of error. Cancelled (which your old version of the script isn’t aware of) means the uplink cancelled the transfer or your node wasn’t fast enough to be among the fastest needed to complete the segment.
If success rates are low it may be some indication that your setup could be improved, though usually it’s location that’s the real issue and you can’t do that much about that.
Here is another screenshot while running the new script on the PowerShell
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell https://aka.ms/pscore6
PS C:\Users\dhiwa\OneDrive\Documents> Unblock-File C:\Users\dhiwa\Downloads\success_rate-master\success_rate-master\successrate.ps1
PS C:\Users\dhiwa\OneDrive\Documents> ./successrate.ps1 -Path "$env:ProgramFiles/Storj/Storage Node/storagenode.log"
========== AUDIT =============
Successful: 76
Recoverable failed: 0
Recoverable Fail Rate: 0.00%
Critically failed: 0
Critical Fail Rate: 0.00%
Success Rate: 100.00%
========== DOWNLOAD ==========
Successful: 2467
Failed: 72
Fail Rate: 2.41%
Canceled: 447
Cancel Rate: 14.97%
Success Rate: 82.62%
========== UPLOAD ============
Successful: 39419
Rejected: 0
Acceptance Rate: 100.00%
---------- accepted ----------
Failed: 136
Fail Rate: 0.09%
Canceled: 120235
Cancel Rate: 75.25%
Success Rate: 24.67%
========== REPAIR DOWNLOAD ===
Successful: 0
Failed: 0
Fail Rate: 0.00%
Canceled: 0
Cancel Rate: 0.00%
Success Rate: 0.00%
========== REPAIR UPLOAD =====
Successful: 238
Failed: 0
Fail Rate: 0.00%
Canceled: 418
Cancel Rate: 63.72%
Success Rate: 36.28%
PS C:\Users\dhiwa\OneDrive\Documents>
``Hi i recive this error ??
./successrate.ps1: riga 1: errore di sintassi vicino al token non atteso “newline”
./successrate.ps1: riga 1: `param(’
can you help me…
Please, checkout the git repository locally, or download a raw script
So i was moving my storagenode folder and is finally done… so now i’m keeping an extra sharp eye on it, because the numbers i got was slightly inconsistent… but all seem fine…
however been running the successrate script a few to many times and i got to thinking…
it would be great if it showed how many errors was in the logs and then maybe a current date.
ofc i could add that myself, but i just figured i would be lazy and suggest it.
to help others xD
Where can I get storagenode.log in Debian?
If you haven’t manually redirected the logs to a file, they are stored by docker. You can run the script as is, without an argument, if you used the default container name. Otherwise execute the script with the container name after it.
docker run -d --restart unless-stopped --stop-timeout 300
-p 28967:28967
-p 14002:14002
-e WALLET=“0xAD0dE316882d3674153F43441E7Cc68f27f8af09”
-e EMAIL=“pablofu*****”
-e ADDRESS=“mystorj01****”
-e STORAGE=“1.8TB”
–mount type=bind,source="/root/.local/share/storj/identity/storagenode/",destination=/app/identity
–mount type=bind,source="/mnt/storjHD",destination=/app/config
–name storagenode storjlabs/storagenode:beta
the path is / mnt / storjHD?
You don’t need the path unless you changed it so it writes to a file in the config.yaml. If you did, then yes, that is likely the path.
You should also remove your email address as this page is public and can be crawled for email addresses for spam lists.
1 Like
this will export the current existing log from docker
$ docker logs storagenode >& /tmp/storagenode.log
else i really like
$ docker logs --tail 20 storagenode --follow
which will give you a live updated log on screen / terminal
else like bright says you can redirect it to a specific location on your computer
that however disables the docker logs functions, because the log file will no longer exit inside the docker stagenode image
3 Likes
I have been wondering for a long time how to get a “live” updating view of the log!!! Thanks so much for the insight.
2 Likes
i like to keep it running on a secondary screen somewhere, so i at a glance can see its working like its suppose to… and it also makes a pretty cool screen saver… and i’ve often noticed weird stuff i wouldn’t have caught otherwise, so i go ctrl +c it and check what that was … and then resumes it …
was planing to make it into a screen saver like the cmatrix on or whatever its named… but haven’t gotten around to it.
good thing you brought me back here… .i was here to look for the newer successrate.sh lol but got distracted…
1 Like