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

Brian Murray brian at ubuntu.com
Fri Oct 20 19:30:17 UTC 2017


The file /var/log/dpkg.log contains the ellipsized lines so yeah I think
dpkg is better place for this.

-- 
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 dpkg.log from journalctl due to ellipses

Status in dpkg package in Ubuntu:
  Confirmed

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/dpkg/+bug/1693948/+subscriptions



More information about the foundations-bugs mailing list