View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010482 | Taler | deployment and operations | public | 2025-10-11 23:34 | 2025-10-20 15:05 |
| Reporter | Christian Grothoff | Assigned To | vecirex | ||
| Priority | low | Severity | minor | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | post-1.0 | ||||
| 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. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-10-11 23:34 | Christian Grothoff | New Issue | |
| 2025-10-11 23:34 | Christian Grothoff | Status | new => assigned |
| 2025-10-11 23:34 | Christian Grothoff | Assigned To | => vecirex |
| 2025-10-12 01:21 | vecirex | Note Added: 0026145 | |
| 2025-10-12 01:24 | vecirex | Note Edited: 0026145 | |
| 2025-10-14 10:23 | vecirex | Note Added: 0026165 | |
| 2025-10-20 15:04 | vecirex | Note Added: 0026204 | |
| 2025-10-20 15:05 | vecirex | Note Edited: 0026204 |
