useless diagnostics in dpkg.log from journalctl due to ellipses
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
init-system-helpers (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Confirmed
|
Medium
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Many of the apport hooks try to include some information about why a service didn't start correctly. One recent report included the following:
May 26 18:39:19 ux305ua-linux systemd[1]: Starting OpenBSD Secure Shell serv....
May 26 18:39:19 ux305ua-linux sshd[2500]: /etc/ssh/
May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.
May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;31mFailed to start OpenBSD Secure She....[0m
May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.
May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.
Hint: Some lines were ellipsized, use -l to show in full.
The actual error information is this:
/etc/ssh/
and
Failed with result 'e....
This is very nearly useless.
We should include the -l parameter as suggested so that we stand a chance of seeing an error that doesn't occur in the first twenty characters of program output.
Thanks
tags: | added: rls-bb-incoming |
summary: |
- useless diagnostics in DpkgTerminalLog from journalctl due to ellipses + useless diagnostics in dpkg.log from journalctl due to ellipses |
Changed in apport (Ubuntu): | |
status: | Incomplete → Confirmed |
affects: | apport (Ubuntu) → dpkg (Ubuntu) |
tags: | added: id-59ea53165a72f7114d0742ef |
affects: | dpkg (Ubuntu) → init-system-helpers (Ubuntu) |
Changed in init-system-helpers (Ubuntu Xenial): | |
importance: | Undecided → Medium |
The manual for journalctl for artful indicates that the default should be the full line.
--no-full, --full, -l
Ellipsize fields when they do not fit in available columns. The default is to show full fields, allowing them to wrap or be truncated by the pager, if one is used.
The old options -l/--full are not useful anymore, except to undo --no-full.
Do you happen to know from which release the crash report you saw had ellipsized lines?