HomeAudit/logs/vaultwarden_sync.log at 45363040f370d7af5608c67119b01e3827a978f0

Files

admin 705a2757c1 Major infrastructure migration and Vaultwarden PostgreSQL troubleshooting

COMPREHENSIVE CHANGES:

INFRASTRUCTURE MIGRATION:
- Migrated services to Docker Swarm on OMV800 (192.168.50.229)
- Deployed PostgreSQL database for Vaultwarden migration
- Updated all stack configurations for Docker Swarm compatibility
- Added comprehensive monitoring stack (Prometheus, Grafana, Blackbox)
- Implemented proper secret management for all services

VAULTWARDEN POSTGRESQL MIGRATION:
- Attempted migration from SQLite to PostgreSQL for NFS compatibility
- Created PostgreSQL stack with proper user/password configuration
- Built custom Vaultwarden image with PostgreSQL support
- Troubleshot persistent SQLite fallback issue despite PostgreSQL config
- Identified known issue where Vaultwarden silently falls back to SQLite
- Added ENABLE_DB_WAL=false to prevent filesystem compatibility issues
- Current status: Old Vaultwarden on lenovo410 still working, new one has config issues

PAPERLESS SERVICES:
- Successfully deployed Paperless-NGX and Paperless-AI on OMV800
- Both services running on ports 8000 and 3000 respectively
- Caddy configuration updated for external access
- Services accessible via paperless.pressmess.duckdns.org and paperless-ai.pressmess.duckdns.org

CADDY CONFIGURATION:
- Updated Caddyfile on Surface (192.168.50.254) for new service locations
- Fixed Vaultwarden reverse proxy to point to new Docker Swarm service
- Removed old notification hub reference that was causing conflicts
- All services properly configured for external access via DuckDNS

BACKUP AND DISCOVERY:
- Created comprehensive backup system for all hosts
- Generated detailed discovery reports for infrastructure analysis
- Implemented automated backup validation scripts
- Created migration progress tracking and verification reports

MONITORING STACK:
- Deployed Prometheus, Grafana, and Blackbox monitoring
- Created infrastructure and system overview dashboards
- Added proper service discovery and alerting configuration
- Implemented performance monitoring for all critical services

DOCUMENTATION:
- Reorganized documentation into logical structure
- Created comprehensive migration playbook and troubleshooting guides
- Added hardware specifications and optimization recommendations
- Documented all configuration changes and service dependencies

CURRENT STATUS:
- Paperless services: ✅ Working and accessible externally
- Vaultwarden: ❌ PostgreSQL configuration issues, old instance still working
- Monitoring: ✅ Deployed and operational
- Caddy: ✅ Updated and working for external access
- PostgreSQL: ✅ Database running, connection issues with Vaultwarden

NEXT STEPS:
- Continue troubleshooting Vaultwarden PostgreSQL configuration
- Consider alternative approaches for Vaultwarden migration
- Validate all external service access
- Complete final migration validation

TECHNICAL NOTES:
- Used Docker Swarm for orchestration on OMV800
- Implemented proper secret management for sensitive data
- Added comprehensive logging and monitoring
- Created automated backup and validation scripts

2025-08-30 20:18:44 -04:00

2.5 KiB

Raw Blame History

[2025-08-30 14:35:05] Starting Vaultwarden data sync to NFS share
[2025-08-30 14:35:05] Step 1: Verifying source Vaultwarden container status
[2025-08-30 14:35:06] Found Vaultwarden container: ef074c4fe727
[2025-08-30 14:35:06] Step 2: Stopping Vaultwarden container for consistent sync
[2025-08-30 14:35:12] Step 3: Verifying NFS mount accessibility
[2025-08-30 14:35:12] SUCCESS: NFS mount is accessible and writable
[2025-08-30 14:35:12] Step 4: Creating backup of current NFS data
[2025-08-30 14:35:13] SUCCESS: NFS backup created: /tmp/vaultwarden_nfs_backup_20250830_143512.tar.gz
[2025-08-30 14:35:13] Step 5: Clearing NFS directory and syncing data
[2025-08-30 14:35:14] Syncing data from source to NFS
[2025-08-30 14:35:19] Step 6: Verifying data sync
[2025-08-30 14:35:20] Source files: 778
[2025-08-30 14:35:20] NFS files: 778
[2025-08-30 14:35:20] SUCCESS: File count matches between source and NFS
[2025-08-30 14:35:20] SUCCESS: SQLite database synced to NFS
[2025-08-30 14:35:21] SUCCESS: RSA key synced to NFS
[2025-08-30 14:35:21] Step 7: Setting proper permissions
[2025-08-30 14:35:23] SUCCESS: Permissions set correctly
[2025-08-30 14:35:23] Step 8: Restarting Vaultwarden container
[2025-08-30 14:35:24] Waiting for Vaultwarden to be healthy
[2025-08-30 14:36:24] SUCCESS: Vaultwarden container is healthy
[2025-08-30 14:36:24] Step 9: Final verification
[2025-08-30 14:36:25] Source database size: 2445312 bytes
[2025-08-30 14:36:25] NFS database size: 2445312 bytes
[2025-08-30 14:36:25] SUCCESS: Database sizes match - sync completed successfully
[2025-08-30 14:36:25]
[2025-08-30 14:36:25] === SYNC COMPLETED SUCCESSFULLY ===
[2025-08-30 14:36:25] ✅ Current Vaultwarden data synced to NFS share
[2025-08-30 14:36:25] ✅ File counts match: 778 files
[2025-08-30 14:36:25] ✅ Database sizes match: 2445312 bytes
[2025-08-30 14:36:25] ✅ Vaultwarden container restarted and healthy
[2025-08-30 14:36:25] ✅ NFS backup created: /tmp/vaultwarden_nfs_backup_20250830_143512.tar.gz
[2025-08-30 14:36:25]
[2025-08-30 14:36:25] Ready to proceed with migration!
[2025-08-30 14:36:25] SUCCESS: Vaultwarden data sync completed successfully!

2.5 KiB Raw Blame History

2.5 KiB

Raw Blame History