package nginx-core 1.10.3-0ubuntu0.16.04.2 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

Bug #1769045 reported by Grégory Becchio on 2018-05-04
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Undecided
Unassigned

Bug Description

thank's

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nginx-core 1.10.3-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
Uname: Linux 4.4.0-122-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Thu May 3 10:06:47 2018
ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
InstallationDate: Installed on 2017-01-02 (486 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt 1.2.26
SourcePackage: nginx
Title: package nginx-core 1.10.3-0ubuntu0.16.04.2 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
UpgradeStatus: No upgrade log present (probably fresh install)

Grégory Becchio (gbecchio) wrote :
Andreas Hasenack (ahasenack) wrote :

From the terminal log:
Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details.
invoke-rc.d: initscript nginx, action "start" failed.
● nginx.service - A high performance web server and a reverse proxy server
   Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since jeu. 2018-05-03 10:06:47 CEST; 4ms ago
  Process: 32008 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=1/FAILURE)
  Process: 32004 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)

mai 03 10:06:46 greg-OptiPlex-9020 nginx[32008]: nginx: [emerg] listen() to [::]:80, backlo...e)
mai 03 10:06:46 greg-OptiPlex-9020 nginx[32008]: nginx: [emerg] listen() to 0.0.0.0:80, bac...e)
mai 03 10:06:46 greg-OptiPlex-9020 nginx[32008]: nginx: [emerg] listen() to [::]:80, backlo...e)
mai 03 10:06:47 greg-OptiPlex-9020 nginx[32008]: nginx: [emerg] listen() to 0.0.0.0:80, bac...e)
mai 03 10:06:47 greg-OptiPlex-9020 nginx[32008]: nginx: [emerg] listen() to [::]:80, backlo...e)
mai 03 10:06:47 greg-OptiPlex-9020 nginx[32008]: nginx: [emerg] still could not bind()
mai 03 10:06:47 greg-OptiPlex-9020 systemd[1]: nginx.service: Control process exited, code=...=1
mai 03 10:06:47 greg-OptiPlex-9020 systemd[1]: Failed to start A high performance web serve...r.
mai 03 10:06:47 greg-OptiPlex-9020 systemd[1]: nginx.service: Unit entered failed state.
mai 03 10:06:47 greg-OptiPlex-9020 systemd[1]: nginx.service: Failed with result 'exit-code'.

Unfortunately the logs are truncated and prevent us from having a good idea about what happened. It looks like it's about listening to port 80, maybe there is another service listening there already?

Could you please try:

sudo apt update
sudo apt -f install

If it still fails, then please show the output of:

sudo systemctl status nginx
sudo netstat -anp

Thanks

Changed in nginx (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for nginx (Ubuntu) because there has been no activity for 60 days.]

Changed in nginx (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers