ClusterCockpit/cc-backend
1
0
Fork 0
mirror of https://github.com/ClusterCockpit/cc-backend synced 2026-04-01 13:37:30 +02:00
Code Issues Packages Releases Activity

Checkpoint: d4b497002f54

Browse Source 
Entire-Session: e301df65-155e-4d0f-b250-3476f2f15115
Entire-Strategy: manual-commit
Entire-Agent: Claude Code
Ephemeral-branch: entire/b1884fd-e3b0c4
This commit is contained in:
Jan Eitzinger
2026-03-26 07:02:37 +01:00
parent 92c1b9bfc1
commit fd51b2aa35
5 changed files with 395 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
d4/b497002f54/0/prompt.txt Normal file
View File

@@ -0,0 +1,7 @@
The shutdown still runs into the 60s timeout. This is the log at shutdown: [INFO] main.go:410: Shutdown signal received
3/26/2026, 6:23:10 AMINFO[INFO] client.go:241: NATS connection closed
3/26/2026, 6:23:10 AMINFO[INFO] archiveWorker.go:223: Initiating archiver shutdown...
3/26/2026, 6:23:10 AMINFO[INFO] archiveWorker.go:238: All archive jobs completed successfully
3/26/2026, 6:23:10 AMINFO[INFO] metricstore.go:286: [METRICSTORE]> Writing to './var/metric-checkpoints'...
3/26/2026, 6:23:10 AMINFO[INFO] archiveWorker.go:121: Archive channel closed, worker exiting
3/26/2026, 6:24:10 AMWARN[WARNING] server.go:448: Shutdown deadline exceeded, forcing exit . What takes that much time, and how can the situation be improved. Add log messages to indicate the shutdown phases and timings. The WAL journals have to be deleted before shutdown!