pcp
[Top] [All Lists]

[Bug 1144] New: when pmcd gives up on a pmda, it should explain what it

To: pcp@xxxxxxxxxxx
Subject: [Bug 1144] New: when pmcd gives up on a pmda, it should explain what it was doing
From: bugzilla-daemon@xxxxxxxxxxx
Date: Mon, 06 Jun 2016 20:16:47 +0000
Auto-submitted: auto-generated
Delivered-to: pcp@xxxxxxxxxxx
Bug ID 1144
Summary when pmcd gives up on a pmda, it should explain what it was doing
Product pcp
Version unspecified
Hardware All
OS Linux
Status NEW
Severity major
Priority P5
Component pcp
Assignee pcp@oss.sgi.com
Reporter fche@redhat.com
CC pcp@oss.sgi.com
Classification Unclassified

When there is a pmcd<->pmda communication breakdown (timeout or whatever), the
pmcd logs are quite opaque as to -why-.  It should log the last request to the
pmda (a fetch?  initial handshaking?  ...?) and any other such nearby info that
can help a pcp developer diagnose what went wrong.

Similarly, a pmda that encounters an EOF from pmcd should log its recent
history, like the type of packet it was just trying to respond to.


You are receiving this mail because:
  • You are on the CC list for the bug.
  • You are the assignee for the bug.
<Prev in Thread] Current Thread [Next in Thread>
  • [Bug 1144] New: when pmcd gives up on a pmda, it should explain what it was doing, bugzilla-daemon <=