Your Mac node's log files no longer grow without limit
TL;DR: On macOS, a node running as a service never trimmed its output and error logs, and one reached 589 MB. From v0.0.134 the node rotates them at 20 MB and keeps three older copies.
If your node runs as a service on a Mac, its log files kept growing for as long as it ran. From v0.0.134, the node keeps them in check itself, and an oversized log gives its space back as soon as you update.
What changes
- Which files.
~/.ee-cdn/logs/ee-cdn-edge-node.out.logand~/.ee-cdn/logs/ee-cdn-edge-node.err.log. - How they rotate. The node checks their size every minute. When one passes 20 MB, it is copied to
.1and emptied in place. The node keeps.1,.2and.3, and drops the oldest. - An existing oversized log is trimmed at the first rotation. Only its last 20 MB is kept, so the space comes back right after you update.
Limits
- A few lines can be lost at each rotation. Lines written in the few milliseconds between the copy and the emptying aren’t kept.
Who it affects
Only nodes running as a service on macOS. Linux under systemd (its logs go to the system journal), Docker and other containers, Windows, and nodes run from a terminal don’t write these files, and nothing changes for them.
What you need to do
If you run a node on a Mac, update it to v0.0.134 or later.