package nginx-core 1.10.3-1ubuntu3.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

Bug #1712696 reported by Thomas Zahreddin on 2017-08-23
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Undecided
Unassigned

Bug Description

maybe conflicting with some stuff from former apache2 installation

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: nginx-core 1.10.3-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Wed Aug 23 23:51:25 2017
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2016-03-16 (524 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt 1.4
SourcePackage: nginx
Title: package nginx-core 1.10.3-1ubuntu3.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: Upgraded to zesty on 2017-07-14 (40 days ago)

Thomas Zahreddin (t-zahreddin) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nginx (Ubuntu):
status: New → Confirmed

got this message while copying/deleting files that were on a local nginx while using webdav protocol.

@Thomas - I beg your pardon I don't know why no one got to this yet :-/

@Kosmonaut - the reported error can only happen on install/upgrade - I'd ask you to file your issue as a new bug to take look at.

About the issue from the log:
Aug 23 23:52:24 thomas-ThinkPad-T430 nginx[20166]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
Aug 23 23:52:24 thomas-ThinkPad-T430 nginx[20166]: nginx: configuration file /etc/nginx/nginx.conf test failed
Aug 23 23:52:24 thomas-ThinkPad-T430 systemd[1]: nginx.service: Control process exited, code=exited status=1
Aug 23 23:52:24 thomas-ThinkPad-T430 systemd[1]: Failed to start A high performance web server and a reverse proxy server.

Could that be a ipv6 setup in the conf but no ipv6 address at all?
I'd have thought it would just not bind to any, but please take a look related to this error message what in your config might be broken as reported by the conf check.

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

Changed in nginx (Ubuntu):
status: Confirmed → Incomplete
Thomas Ward (teward) wrote :

paelzer: No problem I’ve been busy.

This issue comes up when installing on a system that does not support IPv6 at all - not for localhost or for other configuration.

This is an atypical setup so we never addressed what to do in these cases from a packaging perspective. However it ultimately ends up being an end user configuration issue and not a package bug.

dino99 (9d9) wrote :
Changed in nginx (Ubuntu):
status: Incomplete → Invalid
Thomas Ward (teward) wrote :

dino99: that's not why we would have to set this as 'Invalid', and actually applies on a much broader scale. Please consult with me before setting things like this to "Invalid", I"ve been able to replicate this in both 16.04 and 18.04.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers