error.log cleanup in docker instalation?

[fede843]

📑 I have found these related issues/pull requests

• Logrotate on error.log #4917

🛡️ Security Policy

• I have read and agree to Uptime Kuma's Security Policy.

📝 Description

Hi, I have been using the service for a couple of years, and I have noticed the error.log file grows and grows.
I have a simple docker installation. Data content is:

federico@mei /mnt/data/docker/volumes/monitoring/uptime-kuma
 % ls -lah
total 6.7G
drwxr-xr-x 5 root     root 4.0K Sep 20 23:10 .
drwxr-xr-x 3 federico casa 4.0K Sep 20 22:49 ..
drwxr-xr-x 2 root     root 4.0K May 10  2024 docker-tls
-rw-r--r-- 1 root     root 6.0G Sep 22 10:29 error.log
-rwxr-xr-x 1 root     root 604M Sep 22 20:55 kuma.db
-rwxr-xr-x 1 root     root  32K Sep 22 20:56 kuma.db-shm
-rwxr-xr-x 1 root     root 124M Sep 22 20:56 kuma.db-wal
drwxr-xr-x 2 root     root 4.0K May 10  2024 screenshots
drwxr-xr-x 2 root     root 4.0K May 10  2024 upload

There is a related ticket but it was closed without response from user? #4917

Am I missing a setting here or something? First entries in that file are from 2023.

👟 Reproduction steps

none

👀 Expected behavior

Should clean up by itself?

😓 Actual Behavior

Keeps growing

🐻 Uptime-Kuma Version

Version: 1.23.16

💻 Operating System and Arch

Docker on Debian 13, running in a VM in a Proxmox PVE.

🌐 Browser

Chrome

🖥️ Deployment Environment

• Runtime Environment:
  • Docker: Version 28.4.0 (Build 249d679)
  • Docker Compose: Version v2.39.4
• Database:
  • SQLite: Embedded
• Database Storage:
  • Filesystem:
    • Linux: ext4
  • Storage Medium: SSD
• Uptime Kuma Setup:
  • Number of monitors: 14

📝 Relevant log output

[CommanderStorm]

so what does the content of that file roughly look like?
Could you give us the last 100 lines as asked in the other issue?
Could you fill out the Deployment Environment and above fully?

[fede843]

[2023-09-12 10:42:56] TypeError: callback is not a function
    at Socket.<anonymous> (/app/server/server.js:924:17)
[2023-11-28 19:13:47] Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:962:11)
    at Socket._write (node:net:974:8)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Writable.write (node:internal/streams/writable:337:10)
    at console.value (node:internal/console/constructor:305:16)
    at console.log (node:internal/console/constructor:380:26)
    at Logger.log (/app/src/util.js:121:21) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}
...
[2025-09-22 18:15:47] Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:962:11)
    at Socket._write (node:net:974:8)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Writable.write (node:internal/streams/writable:337:10)
    at console.value (node:internal/console/constructor:305:16)
    at console.log (node:internal/console/constructor:380:26)
    at Logger.log (/app/src/util.js:143:21) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

those are the first entry and the last entry. I guess it is most the same in between?