We understand that. The point is, that this is not an error, not even a warning, and definitely does not deserve 1kb worth of stack shots in the log file every time this happens. Which is multiple times per second, resulting in tens of gigabytes of text garbage on storage noes.
This has been brought up before, and such disregard of storage resources does not look good, let alone making finding anything remotely important in that log file entirely pointless.
The fix requires one line change to reduce change log severity from error to info, and does not deserve lengthy discussion.
Let’s split this thread to its own topic please.
Edit: few last log sizes on my node (rotates daily at midnight):
storj# ls -hl storj.log*(om[1,6])
-rw------- 1 root wheel 5.6M Oct 10 00:17 storj.log
-rw------- 1 root wheel 46M Oct 10 00:00 storj.log.0.bz2
-rw------- 1 root wheel 2.0G Oct 9 00:00 storj.log.1.bz2
-rw------- 1 root wheel 48M Oct 8 00:00 storj.log.2.bz2
-rw------- 1 root wheel 46M Oct 7 00:00 storj.log.3.bz2
-rw------- 1 root wheel 50M Oct 6 00:00 storj.log.4.bz2
See that 2.0GiB bz2 compressed, highly redundant, text file? I’m afraid to decompress it to check the actual size…