View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010482 | Taler | deployment and operations | public | 2025-10-11 21:34 | 2025-11-19 23:03 |
| Reporter | Christian Grothoff | Assigned To | vecirex | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | low | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 1.2 | Fixed in Version | 1.2 | ||
| Summary | 0010482: pixel /tmp > 90% full due to loki | ||||
| Description | Loki wrote too much to /tmp. Restarting it didn't help, so I stopped, cleaned /tmp and restarted it. Still, something is bad and we should figure out how to teach Loki to not do this. | ||||
| Tags | No tags attached. | ||||
| ACK, will do: related to the other grafana/loki ticket #10476. | |
| Update: Same (common) solution attempt as for #10476, cf. admin log: b5f410150bbb3be12f149e9cf609759a71101310 | |
| Update: Cache seems never to be cleared, easiest solution to be: regularly close loki, clear cache, start loki. Only restarting it and w/ cache cleared beforehands or afterwards could mean data loss of working data loki was / is on. To be solved via systemd in the process of lifeline setup. | |
| Update: I put a systemd service in place, freeing resources after stopping and starting loki after 4hrs, making sure it's first really stopped before cleaning cache; and making also sure it's running afterwards again; loki-restart timer already active: [snip] systemctl status loki-restart.timer ● loki-restart.timer - Run loki restart script every 4 hours Loaded: loaded (/etc/systemd/system/loki-restart.timer; enabled; preset: e> Active: active (waiting) since Tue 2025-10-21 15:41:42 CEST; 14min ago Invocation: d960fbe2456d404d804c41681f31c180 Trigger: Tue 2025-10-21 19:41:42 CEST; 3h 45min left Triggers: ● loki-restart.service [/snip] See admin-log for today. | |
| Closing tickets done | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-10-11 21:34 | Christian Grothoff | New Issue | |
| 2025-10-11 21:34 | Christian Grothoff | Status | new => assigned |
| 2025-10-11 21:34 | Christian Grothoff | Assigned To | => vecirex |
| 2025-10-11 23:21 | vecirex | Note Added: 0026145 | |
| 2025-10-11 23:24 | vecirex | Note Edited: 0026145 | |
| 2025-10-14 08:23 | vecirex | Note Added: 0026165 | |
| 2025-10-20 13:04 | vecirex | Note Added: 0026204 | |
| 2025-10-20 13:05 | vecirex | Note Edited: 0026204 | |
| 2025-10-21 14:10 | vecirex | Note Added: 0026215 | |
| 2025-10-21 14:18 | vecirex | Note Edited: 0026215 | |
| 2025-10-21 14:19 | vecirex | Status | assigned => informing |
| 2025-10-21 14:19 | vecirex | Resolution | open => fixed |
| 2025-11-06 00:28 | Christian Grothoff | Fixed in Version | => 1.2 |
| 2025-11-06 00:28 | Christian Grothoff | Target Version | post-1.0 => 1.2 |
| 2025-11-19 23:03 | vecirex | Note Added: 0026560 | |
| 2025-11-19 23:03 | vecirex | Status | informing => closed |