Bug 1330176 - Each 'virt-top' exit/stop logs a message in /var/log/messages
Summary: Each 'virt-top' exit/stop logs a message in /var/log/messages
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-top
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1420851
TreeView+ depends on / blocked
 
Reported: 2016-04-25 14:19 UTC by Chetan Nagarkar
Modified: 2019-10-10 11:58 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-27 21:29:16 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Chetan Nagarkar 2016-04-25 14:19:16 UTC
Description of problem:

Each 'virt-top' exit/stop logs a message in /var/log/messages. Error message as below,
"End of file while reading data: Input/output error"



Version-Release number of selected component (if applicable):
RHEL 7.2

How reproducible:

100%

Steps to Reproduce:
1. Run "Virt-top"
2. exit it with either 'q' or "Ctrl + C"

Actual results:

In /var/log/messages, Error logged as "End of file while reading data: Input/output error" each and every successful run of "virt-top"

Expected results:
No logs should be generated after every interruption or clean exit.

Additional info:

Case no: 01622013
Account Name: Wake County Public Schools
Customer reported this bug as not harmful but need attention as 'virt-top' running every 5 minutes in their application and creating the additional log lines in messages.

Comment 1 Richard W.M. Jones 2016-04-25 14:29:47 UTC
Indeed, I can reproduce this as well.  It seems harmless as you say,
but it should be doing it!

Comment 3 Richard W.M. Jones 2016-07-06 10:34:56 UTC
virt-top is not on the Approved Components List for RHEL 7.3, so
I cannot fix this at this time.

Comment 4 Richard W.M. Jones 2017-03-28 13:47:49 UTC
Moving to RHEL 7.5 as this bug is cosmetic.


Note You need to log in before you can comment on or make changes to this bug.