Thanks Brian; should we retarget this bug to dpkg to get it to show
different output? or is it still apport that is collecting ellipsized
logs?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to