The hard drive usage is very high

[arrogantrabbit]

@havri1

It’s unbelievable that it always has some problem

Any software always has unknowable number of bugs. Known number of known bugs, and unknown number of unknown bugs. Always.(even for software that does not interact with anything else – which is not the case in the real world – it’s fundamentally related to halting problem).

Dev team balances priorities between fixing bugs and implementing new features. This is a very low priority bug.

They also cannot possibly fix the bug they don’t know about. Nobody submitted GitHub issue on this. Whining on forums is drastically not the same thing.

I’m not sure why are you surprised.

TLDR: This bug does not bother me enough to lift a finger. If it bothers you – submit GitHub issue (or, better yet, PR), and track it down to resolution.

I’ve submitted requests for issues that bothered me in the past.

[havri1]

Thank you, now I understand. Based on the description, I added the line to the config, and now it only logs ERROR entries, so there’s much less output. I hope I won’t have any more problems, and the node can continue running."

[havri1]

I don’t think I’m alone with this issue, as you can see, others have struggled with it too. That’s exactly why I described my problem. It’s just a bit frustrating that I solve one problem, and then the next one comes… this has been going on for a month.

[Alexey]

Maybe I do not babysit my nodes too much, I do have the growing logs as well. However, I do have a logrotation configured. So, not a problem for me.

[havri1]

I am interested in a solution. For example, to delete after 500MB or entries older than 48 hours. Could be a script, PowerShell?

[Alexey]

Windows?
Either a logrotate as well (it’s called winlogrotate), or the script:

Native logs rotation in Windows with a simple PowerShell script

Hello, Unfortunately, in the current windows version of the Storage Node there is no way to rotate or limit the size of the generated logs files. You cannot delete them from the GUI because they are locked by the services processes. Using Clear-Content in PowerShell to reset the files works but there is no easy solution if you want to keep a few days / weeks of logs. I have written a small PowerShell script that can rotate the Storjs Logs without the need of Stop>Start the services to release …

However, since I also have a Windows Docker Desktop nodes, then I run the crond service in WSL2, and used the same configuration for logrotate there:

$ cat /etc/logrotate.d/storagenodes
/mnt/x/storagenode2/storagenode.log
/mnt/y/storagenode3/storagenode.log
/mnt/w/storagenode5/storagenode.log
{
    su root root
    dateext
    rotate 24
    monthly
    copytruncate
    compress
    missingok
    notifempty
}

Of course, I redirected logs for the Windows node to the data location, i.e. y:\storagenode3\ with the parameter log.output: in my config.yaml:

log.output: winfile:///Y:\storagenode3\\storagenode.log

And to run a crond service I executed in WSL2:

sudo service cron start

While it’s running, the logrotate is working for both - docker nodes and the Windows service node.