Node log to file stopped updating after hitting a particular size limit

log.output: “/app/config/node.log”

I’ve noticed my node.log stopped updating after it hit a size of (22,167,248 bytes).

  • Has anyone else noticed this?
  • Is there a possible issue in how the node operates if the node.log reaches a certain size?
  • Is there an additional command that can be used to split and create a new node.log file, which would create incremental node.log files as an archive?

I had to rename the log and restart the node to resume back to normal operation with a new empty node.log file

Which operating system are you using ?

This might have been an anomaly as I could re-create it, however I would still like to know:

  • Is there an additional command that can be used to split and create a new node.log file, which would create incremental node.log files as an archive?

Only the standard logrotate.
The storagenode doesn’t have any such functions as far as I know.

How to split logs

This works only if you didn’t redirect the log.

1 Like