How did I fix «Failed to start nginx.service - LSB: starts the nginx web server» in Debian 12?

dmitrii_fediuk · October 19, 2023, 5:49pm

github.com/dmitrii-fediuk/5.9.188.84

Nginx became down after switching Debian 10 from SysVinit to Systemd: «Failed to start nginx.service - LSB: starts the nginx web server»

opened 06:10PM - 18 Sep 23 UTC

closed 05:19AM - 19 Oct 23 UTC

Nginx Systemd

![2023-09-18--21-14-44](https://github.com/dmitrii-fediuk/5.9.188.84/assets/8320…4/225a95a7-cce8-4c85-aef8-0c3ed8961637) ``` × nginx.service - LSB: starts the nginx web server Loaded: loaded (/etc/init.d/nginx; generated) Active: failed (Result: exit-code) since Tue 2023-09-19 00:00:05 +06; 13min ago Duration: 16h 6min 37.314s Docs: man:systemd-sysv-generator(8) Process: 592402 ExecStart=/etc/init.d/nginx start (code=exited, status=1/FAILURE) CPU: 18ms Sep 19 00:00:05 5-9-188-84 systemd[1]: nginx.service: Found left-over process 4141124 (nginx) in control group while starting unit. Ignoring. Sep 19 00:00:05 5-9-188-84 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 19 00:00:05 5-9-188-84 systemd[1]: Starting nginx.service - LSB: starts the nginx web server... Sep 19 00:00:05 5-9-188-84 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE Sep 19 00:00:05 5-9-188-84 systemd[1]: nginx.service: Failed with result 'exit-code'. Sep 19 00:00:05 5-9-188-84 systemd[1]: nginx.service: Unit process 4141116 (nginx) remains running after unit stopped. Sep 19 00:00:05 5-9-188-84 systemd[1]: nginx.service: Unit process 4141119 (nginx) remains running after unit stopped. Sep 19 00:00:05 5-9-188-84 systemd[1]: nginx.service: Unit process 4141122 (nginx) remains running after unit stopped. Sep 19 00:00:05 5-9-188-84 systemd[1]: nginx.service: Unit process 4141124 (nginx) remains running after unit stopped. Sep 19 00:00:05 5-9-188-84 systemd[1]: Failed to start nginx.service - LSB: starts the nginx web server. ```

dmitrii_fediuk · October 19, 2023, 5:49pm

A temporary workaround is a reboot.