Version: @memtensor/memos-local-plugin 2.0.16, installed via install.sh (Hermes Agent integration)
install.sh launches the bridge daemon with a plain redirect and no rotation:
# install.sh:1055-1063
local daemon_log="${prefix}/logs/daemon-start.log"
...
nohup "${node_bin}" "${bridge_entry}" --agent=hermes --daemon >"${daemon_log}" 2>&1 &No size cap, no logrotate hookup, no truncation on restart. Measured across three long-running installs: 59.3 MB / 287,895 lines on the oldest, 10.8 MB and 9.1 MB on two others — still growing, actively written.
The volume itself points at a second bug. In the most recent 5,000 lines of the 59 MB log: 2,150 are WARN/ERROR (~43%), 644 are http.exception, 274 are fetch failed. All 644 http.exception entries carry transient=false — none are retried. A rotation policy alone would hide this; the firehose is the daemon treating what looks like a retryable condition (fetch failed) as terminal on every occurrence.
Separately, historical crash churn (ERR_MODULE_NOT_FOUND for a missing tsx, 186 stack frames) accounts for part of the file's total size but doesn't reproduce in the last 5,000 lines — that part is fixed/settled, not a current concern.
Ask:
- Rotate/cap
daemon-start.log in install.sh (or move to a proper logger with rotation).
- Look at why
http.exception is uniformly transient=false and never retried — fetch failed in particular looks like it should be retryable.
Happy to share the full recent-lines sample if useful.
Version:
@memtensor/memos-local-plugin2.0.16, installed viainstall.sh(Hermes Agent integration)install.shlaunches the bridge daemon with a plain redirect and no rotation:No size cap, no logrotate hookup, no truncation on restart. Measured across three long-running installs: 59.3 MB / 287,895 lines on the oldest, 10.8 MB and 9.1 MB on two others — still growing, actively written.
The volume itself points at a second bug. In the most recent 5,000 lines of the 59 MB log: 2,150 are WARN/ERROR (~43%), 644 are
http.exception, 274 arefetch failed. All 644http.exceptionentries carrytransient=false— none are retried. A rotation policy alone would hide this; the firehose is the daemon treating what looks like a retryable condition (fetch failed) as terminal on every occurrence.Separately, historical crash churn (
ERR_MODULE_NOT_FOUNDfor a missingtsx, 186 stack frames) accounts for part of the file's total size but doesn't reproduce in the last 5,000 lines — that part is fixed/settled, not a current concern.Ask:
daemon-start.logininstall.sh(or move to a proper logger with rotation).http.exceptionis uniformlytransient=falseand never retried —fetch failedin particular looks like it should be retryable.Happy to share the full recent-lines sample if useful.