http://bugzilla.opensuse.org/show_bug.cgi?id=996203 http://bugzilla.opensuse.org/show_bug.cgi?id=996203#c19 Archie Cobbs <archie.cobbs@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |archie.cobbs@gmail.com --- Comment #19 from Archie Cobbs <archie.cobbs@gmail.com> --- FWIW, I just saw a similar problem. Totally out of the blue. I have an RPM that includes the SSL certificate. To update the SSL certificate I build and install a new version of the RPM. The RPM contains this script: %post # Reload apache if systemctl -q is-active apache2.service; then systemctl reload-or-try-restart apache2.service fi This has worked normally for years on 10+ different machines. Suddenly today instead I got this error: apache2.service: Failed at step NAMESPACE spawning /usr/sbin/start_apache2: No such file or directory Here is the relevant journalctl output: Nov 22 12:42:19 prod systemd[1]: Stopping The Apache Webserver... Nov 22 12:42:19 prod systemd[2793]: apache2.service: Failed at step NAMESPACE spawning /usr/sbin/start_apache2: No such file or directory Nov 22 12:42:19 prod systemd[1]: apache2.service: Control process exited, code=exited status=226 Nov 22 12:42:19 prod systemd[1]: Stopped The Apache Webserver. Nov 22 12:42:19 prod systemd[1]: apache2.service: Unit entered failed state. Nov 22 12:42:19 prod systemd[1]: apache2.service: Failed with result 'exit-code'. Nov 22 12:42:19 prod systemd[1]: Starting The Apache Webserver... Nov 22 12:42:19 prod systemd[1]: Started The Apache Webserver. I then logged in and did "systemctl restart apache2" and everything was fine. Running "rpm -V apache2" showed nothing amiss. This smells to me like some kind of systemd internal race condition bug. Let me know if I can provide more info. Versions: openSUSE Leap 15.0 apache2-2.4.33-lp150.2.23.1.x86_64 systemd-234-lp150.20.15.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.