action #131096
Updated by okurz 11 months ago
## Observation ``` martchus@schort-server:~> sudo journalctl --since '2 days ago' -u ca-certificates Jun 18 03:01:48 schort-server systemd[1]: Starting Update system wide CA certificates... Jun 18 03:01:49 schort-server update-ca-certificates[29527]: mv: cannot stat '/var/lib/ca-certificates/ca-bundle.pem.new': No such file or directory Jun 18 03:01:49 schort-server systemd[1]: ca-certificates.service: Main process exited, code=exited, status=1/FAILURE Jun 18 03:01:49 schort-server systemd[1]: ca-certificates.service: Failed with result 'exit-code'. Jun 18 03:01:49 schort-server systemd[1]: Failed to start Update system wide CA certificates. -- Boot 41358baf1d8748c28a50ae58ad0915be -- Jun 18 03:34:27 schort-server systemd[1]: Starting Update system wide CA certificates... Jun 18 03:34:36 schort-server systemd[1]: ca-certificates.service: Deactivated successfully. Jun 18 03:34:36 schort-server systemd[1]: Finished Update system wide CA certificates. ``` The situation fixed itself after a reboot and until then it didn't cause further problems. However, the unit was in the failed state temporarily triggering an alert. ## Suggestions * Might be an upstream bug. If not exists report it * Take a look into /usr/lib/ca-certificates/update.d/99certbundle.run , like https://github.com/openSUSE/ca-certificates/blob/master/certbundle.run#L37, might be easy to provide upstream contribution pull request to fix in https://github.com/openSUSE/ca-certificates , package is https://build.opensuse.org/package/show/openSUSE:Factory/ca-certificates