hakwerk
All accounts and certificates get lost during server restart
I recently moved my installation from a stand alone version to docker. Installation and restoring the backup worked ok, except that restoring the backup at the intial admin creation restore did not import accounts and certificates. After a manual import all data was there. Server is a ubuntu server container under proxmox.
However, after every restart of the server all data is lost. 0 accounts and 0 certificates. The system is showing crl update errors due to missing certificates.
/opt/logs/commander.log ... mv: inter-device move failed: '/tmp/250801-113028_ppkiserver/nginx_ssl/ssl' to '/etc/nginx/ssl/ssl'; unable to remove target: Directory not empty mv: inter-device move failed: '/tmp/250801-113028_ppkiserver/nginx_ssl/ssl' to '/etc/nginx/ssl/ssl'; unable to remove target: Directory not empty
In all other logs I cannot spot any issues, although I might have missed something.
Any ideas?
Oliver
I have now updated to the newest version, and now labra refuses to load the backup at all. Error in line 293…
I for now give up on it. The few servers I run which need a certificate get a manually installed certificate with 10 years life time. If this expires, the world and the cert system might be totally different anyhow.
Oliver
Im getting the same issue that restarting wipes all accounts and certificates but due to this:
bmysql-1 | 2025-08-19 10:56:48 36 [Warning] Aborted connection 36 to db: 'boulder_sa_integration' user: 'root' host: '10.77.77.132' (Got an error reading communication packets)
bmysql-1 | 2025-08-19 10:56:48 40 [Warning] Aborted connection 40 to db: 'boulder_sa_integration' user: 'root' host: '10.77.77.132' (Got an error reading communication packets)
bmysql-1 | 2025-08-19 10:56:48 34 [Warning] Aborted connection 34 to db: 'boulder_sa_integration' user: 'root' host: '10.77.77.132' (Got an error reading communication packets)
bmysql-1 | 2025-08-19 10:56:48 33 [Warning] Aborted connection 33 to db: 'boulder_sa_integration' user: 'root' host: '10.77.77.132' (Got an error reading communication packets)
bmysql-1 | 2025-08-19 10:56:48 32 [Warning] Aborted connection 32 to db: 'boulder_sa_integration' user: 'root' host: '10.77.77.132' (Got an error reading communication packets)
bmysql-1 | 2025-08-19 10:56:48 31 [Warning] Aborted connection 31 to db: 'boulder_sa_integration' user: 'root' host: '10.77.77.132' (Got an error reading communication packets)
That error in the bmysql container is not causing this issue. It happens because of some circular dependency between boulder components. That error should go away after a short while...
"That error should go away after a short while..." I cannot confirm that. The error does not go away within several hours.
Oliver