apport hides systemd postinst service start failure error messages

Bug #1587791 reported by Robie Basak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

See bug 1587695 for example. Expected: amavis' failure reason in the original bug report. Actual: we are only told that it failed, not why, which systemd knows anyway and which the service correctly reported.

This is a regression from before systemd-boot, since before DpkgTerminalLog contained the message.

This problem hinders bug triage.

Tags: systemd-boot
Revision history for this message
Robie Basak (racb) wrote :

10:41 <pitti> rbasak: hm, no amavis messages in https://launchpadlibrarian.net/262668434/JournalErrors.txt, so I'm not sure if that'd actually help

10:41 <pitti> rbasak: might be that this is a forking service which only outputs to log files, not to stdout/err?

10:42 <pitti> rbasak: ah, wait, this only shows messags with priority >= warning, so maybe that's why

10:42 <pitti> rbasak: yeah, I guess we can amend the ubuntu hook for package failures to include the status

Revision history for this message
Robie Basak (racb) wrote :

In my example, "systemctl status amavis" did show me the error, so presumably if systemd has it this is because the init.d script did output the error to stdout or stderr. So I guess it's the priority as pitti suggests.

Revision history for this message
Robie Basak (racb) wrote :

Could this be fixed by the solution for bug 1596056?

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.