May 20 17:41:49 systemd: rvice: Failed with result 'exit-code'. May 20 17:41:49 systemd: rvice: Unit entered failed state. May 20 17:41:49 systemd: Failed to start A high performance web server and a reverse proxy server. May 20 17:41:49 systemd: rvice: Control process exited, code=exited status=1 May 20 17:41:49 nginx: nginx: still could not bind() May 20 17:41:49 nginx: nginx: listen() to :80, backlog 511 failed (98: Address already in use) May 20 17:41:48 nginx: nginx: listen() to :80, backlog 511 failed (98: Address already in use) Process: 11210 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on master_process on (code=exited, status=0/SUCCESS) Process: 11212 ExecStart=/usr/sbin/nginx -g daemon on master_process on (code=exited, status=1/FAILURE) Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)Īctive: failed (Result: exit-code) since Sat 17:41:49 CEST 1min 30s ago
rvice - A high performance web server and a reverse proxy server. Nginx-extras (< 1.10.0-0ubuntu0.16.04.4.1~) but it is not going to be installedĮ: Unable to correct problems, you have held broken packages. Nginx-light (< 1.10.0-0ubuntu0.16.04.4.1~) but it is not going to be installed or Nginx-full (< 1.10.0-0ubuntu0.16.04.4.1~) but it is not going to be installed or Nginx-extras (>= 1.10.0-0ubuntu0.16.04.4) but it is not going to be installedĭepends: nginx-core (< 1.10.0-0ubuntu0.16.04.4.1~) but it is not going to be installed or Nginx-light (>= 1.10.0-0ubuntu0.16.04.4) but it is not going to be installed or Nginx-full (>= 1.10.0-0ubuntu0.16.04.4) but it is not going to be installed or Nginx : Depends: nginx-core (>= 1.10.0-0ubuntu0.16.04.4) but it is not going to be installed or The following packages have unmet dependencies: The following information may help to resolve the situation: Requested an impossible situation or if you are using the unstableĭistribution that some required packages have not yet been created # Give Passenger a chance to clean up before being killed by systemd. # Use TERM instead of QUIT to prevent Nginx from leaving stale Unix socket and failing the next start ()ĮxecStop=-/sbin/start-stop-daemon -quiet -stop -retry TERM/5 -pidfile /run/nginx.pid # SIGKILL to all the remaining processes in the process group (KillMode=mixed).ĭescription=A high performance web server and a reverse proxy serverĮxecStartPre=/usr/sbin/nginx -t -q -g 'daemon on master_process on 'ĮxecStart=/usr/sbin/nginx -g 'daemon on master_process on 'ĮxecReload=/usr/sbin/nginx -g 'daemon on master_process on ' -s reload # After another 5s (TimeoutStopSec=5), and if nginx is alive, systemd sends # and sends SIGTERM (fast shutdown) to the main process. # If, after 5s (-retry QUIT/5) nginx is still running, systemd takes control # ExecStop sends SIGSTOP (graceful stop) to the nginx process. Результаты cat /lib/systemd/system/rvice : # Stop dance for nginx May 20 17:03:53: rvice: Failed with result 'exit-code'. May 20 17:03:53: rvice: Unit entered failed state. May 20 17:03:53: Failed to start A high performance web server and a reverse proxy server. May 20 17:03:53: rvice: Control process exited, code=exited status=203 May 20 17:03:53: rvice: Failed at step EXEC spawning /usr/sbin/nginx: No such file or directory May 20 17:03:53: Starting A high performance web server and a reverse proxy server. See "systemctl status rvice" and "journalctl -xe" for details. Результаты service nginx restart : Job for rvice failed because the control process exited with error code.
0 kommentar(er)
