package nginx-full 1.10.3-1ubuntu3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

Bug #1674077 reported by Ignacio de Castro Pérez on 2017-03-19

This bug report will be marked for expiration in 22 days if no further activity occurs. (find out why)

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Undecided
Unassigned

Bug Description

I don't konow about it

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: nginx-full 1.10.3-1ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-13.15-lowlatency 4.10.1
Uname: Linux 4.10.0-13-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Sun Mar 19 10:18:30 2017
ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2017-03-17 (1 days ago)
InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.4~rc2
SourcePackage: nginx
Title: package nginx-full 1.10.3-1ubuntu3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

ChristianEhrhardt (paelzer) wrote :

Hi Ignacio,
thank you for your report and your help to make Ubuntu better.
The logs that were attached did not lead me to an obvious error, mostly those issues are caused by incomplete or broken configurations. On package updates or reinstalls without former purging this config then makes the (re)start fail and cause an issue like the one you are facing.

If you happen to have no custom nginx config at all yet consider purging and reinstalling.
If you have a custom config consider disabling it for the upgrade and then step by step enable your config bits to find what breaks it.

ChristianEhrhardt (paelzer) wrote :

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: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers