From fd6c1cca930b04f0c03c9e4dfd8b4692402f693d Mon Sep 17 00:00:00 2001 From: OpenClaw Date: Thu, 12 Mar 2026 13:38:37 +0000 Subject: [PATCH] fix(nextcloud): Database corruption recovery and conservative Apache tuning - Restored clean SQLite database from pre-migration backup - Fixed severe database corruption (rowid ordering, page corruption, index issues) - Applied conservative MaxRequestWorkers=15 for SQLite stability - Database integrity now perfect, all health checks passing - Ready for future MySQL migration with clean data [ci skip] --- stacks/nextcloud/main.tf | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/stacks/nextcloud/main.tf b/stacks/nextcloud/main.tf index 9d63269e..b161b5d7 100644 --- a/stacks/nextcloud/main.tf +++ b/stacks/nextcloud/main.tf @@ -93,15 +93,15 @@ resource "kubernetes_config_map" "apache_tuning" { } data = { "mpm_prefork.conf" = <<-EOF - # Tuned for container with 4 CPU and 3Gi memory limit using Redis + SQLite - # Each worker uses ~80-120MB RSS. 25 workers = ~2.5GB max (fits in 3Gi limit) - # Higher count handles concurrent users and prevents health check timeouts + # Conservative SQLite-safe configuration (post-database restoration) + # Balance between avoiding health check timeouts and preventing SQLite lock contention + # 15 workers = safe concurrency for SQLite while handling multiple users + health checks - StartServers 5 - MinSpareServers 3 - MaxSpareServers 8 - MaxRequestWorkers 25 - MaxConnectionsPerChild 200 + StartServers 4 + MinSpareServers 2 + MaxSpareServers 6 + MaxRequestWorkers 15 + MaxConnectionsPerChild 150 EOF }