log sink read errors are not logged

Bug #1852815 reported by John A Meinel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
John A Meinel
2.6
Fix Released
High
John A Meinel

Bug Description

We are seeing log sink read disconnect messages on Prodstack. However, bumping logging to a higher level isn't useful for debugging because we print:

  logger.Debugf("disconnected, %p", socket)

So we declare that it was disconnected but we just print the hex socket identifier, which isn't useful. We need to log the error.

Revision history for this message
John A Meinel (jameinel) wrote :
Changed in juju:
milestone: 2.7-rc5 → none
Harry Pidcock (hpidcock)
Changed in juju:
status: In Progress → Fix Released
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.