** Description changed:
+ [Impact]
+
+ This issue makes it impossible to reliably determine the cause of a
+ postinstallation failure bug during the installation or upgrade attempt
+ of an nginx binary package. A large number of the bugs have tied back
+ to "Postinstall exited with error code" issues, but that's all we have
+ about it. Additional data needs to be collected, which apport hooks
+ solve.
+
+
+ [Test Case]
+
+ This does not resolve the issue with an installation failure. It does
+ increase the amount of information made available by the bug report.
+
+ (1) Have Apache or some other thing binding to port 80
+ (2) Install nginx-common and one of the following: nginx-core nginx-light
nginx-full nginx-extras
+ (3) Run `apport-bug` on the crash report and review the data.
+
+ The problem is reproduced if all we get from the dpkg logs is something
+ about the job failing to start, with no additional information.
+
+ Testing the fix, when you run the report, you will get
+ "Journalctl_Nginx.txt" and "SystemctlStatusFull_Nginx.txt" files in the
+ report data. These will contain the output of the two commands that the
+ system says you should run to get more information about the failure,
+ and includes it in the report.
+
+
+ [Regression Potential]
+
+ None. All this adds is an apport hook, which has been tested on both
+ Wily and Vivid.
+
+
+ [Other Info]
+
+ I know for a fact that Seth Arnold and Robie Basak will praise these
+ apport hooks, if only because we will actually be able to debug
+ installation and upgrade failures in which nginx binaries are failing to
+ install due to some issue with the job start process.
+
+
+ [Original Description]
+
This is against the 'nginx' package because apport hooks need added here
for Vivid and Wily.
Currently, systemd and stderr and Apport do not pull in enough
information for bug triage and handling to be done.
We have several Vivid bugs now which show this - they're all for the
same version of the package, in Wily, but different binaries, all with
the Package problem type, and a postinstallation script failure. But
that's it, there's no information of the errors, or anything.
To that end, we need to expand what Apport pulls in, to include output
from `journalctl -xe --unit=nginx.service` and `systemctl -l status
nginx.service` in order to get useful information for Package class
bugs.
I have given this a Medium importance, as there's no useful information
in bug reports of the Package class currently that could allude to why
the postinst scripts failed.
** Changed in: nginx (Ubuntu Vivid)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1472683
Title:
Nginx bug reports for 'package' problem type are not providing useful
data for Vivid and later
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1472683/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
