Alexey
March 30, 2022, 7:05pm
5
I could only suggest to stop the storagenode and rename the log, then start the storagenode back - it will create a new log with less size and then after a while you can run this script again.
The alternative is to use this version:
The original successrate.ps1 script from @Alexey was having problems on my machine with high memory usage whilst running on larger log files. So I rewrote it slightly to read the log one line at a time, calculate all the variables as it goes and then print out at the end. It’s between 10% and 30% faster to run on my machine using an identical log file.
param(
$Path = "C:\Program Files\Storj\Storage Node\storagenode - Copy.log"
)
$auditsSuccess=0
$auditsFailed=0
$auditsFailedCritical=0
$dl…
But it’s better to rename/archive your logs from time to time.
About logs…
If the log is too big, you can open it with Notepad++ or other coding editor.
Available log levels are: debug , info , warn , error , none .
You can open/edit the config.yaml with Notepad++ or Visual Studio Code or some other coding editor and change the log level. The error level makes the smallest log, but with the fewest info. The debug is the richest in info and makes a huge log.
You cand delete the storagenode.log and storagenode-updater.log anytime, after you stop both serv…
1 Like