[Bug 1693948] Re: useless diagnostics from journalctl due to ellipses

[Brian Murray]

Looking at manpages for previous releases of Ubuntu they all contain the
same information about --full for journalctl.  I did find lines being
ellipsized in a DpkgTerminalLog.txt file. Is that what you were looking
at? An example:

Instalowanie nowej wersji pliku konfiguracyjnego /etc/apparmor.d/abstractions/libvirt-qemu ...
Setting up libvirt-daemon dnsmasq configuration.
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
   Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2017-03-07 13:07:21 CET; 44ms ago
  Process: 1289 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=2)
  Process: 1272 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS)
      CPU: 25ms

mar 07 13:07:21 Leoo-G5 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server...
mar 07 13:07:21 Leoo-G5 dnsmasq[1272]: dnsmasq: syntax check OK.
mar 07 13:07:21 Leoo-G5 dnsmasq[1289]: dnsmasq: failed to create listening socket for 127.0.0.1: Address al… in use
mar 07 13:07:21 Leoo-G5 systemd[1]: dnsmasq.service: Control process exited, code=exited status=2
mar 07 13:07:21 Leoo-G5 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
mar 07 13:07:21 Leoo-G5 systemd[1]: dnsmasq.service: Unit entered failed state.
mar 07 13:07:21 Leoo-G5 systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.

** Changed in: apport (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1693948

Title:
  useless diagnostics in DpkgTerminalLog from journalctl due to ellipses

Status in apport package in Ubuntu:
  Incomplete

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/sshd_config line 64: miss....
  May 26 18:39:19 ux305ua-linux systemd[1]: ssh.service: Main process exited, ...a
  May 26 18:39:19 ux305ua-linux systemd[1]: Failed to start OpenBSD Secure She....
  May 26 18:39:19 ux305ua-linux systemd[1]: ssh.service: Unit entered failed s....
  May 26 18:39:19 ux305ua-linux systemd[1]: ssh.service: Failed with result 'e....
  Hint: Some lines were ellipsized, use -l to show in full.

  
  The actual error information is this:

  /etc/ssh/sshd_config line 64: miss....
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1693948/+subscriptions