Bug 1383915 - [RFE] Add process identifier in spice client log file
Summary: [RFE] Add process identifier in spice client log file
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: mingw-virt-viewer
Version: 8.0
Hardware: x86_64
OS: All
high
medium
Target Milestone: rc
: ---
Assignee: Default Assignee for SPICE Bugs
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-12 07:13 UTC by Tim Speetjens
Modified: 2020-11-14 11:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-25 08:17:38 UTC
Type: Feature Request
Target Upstream Version:


Attachments (Terms of Use)

Description Tim Speetjens 2016-10-12 07:13:19 UTC
Description of problem:
When debugging SPICE issues, that are reproducible only when two spice connections are open, the single log file written to by both becomes very difficult to read.

Version-Release number of selected component (if applicable):
Windows SPICE client, packaged in
rhevm-spice-client-x64-msi-3.6-6.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. Setup SPICE client debug logging
2. Open multiple connections
3. Watch logging to appear inside this file for both windows/connections

Actual results:
All logging appears in one single log file

Expected results:
Each window/spice client process should log in its own log file

Additional info:

Comment 3 Sandro Bonazzola 2019-01-28 09:44:16 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 5 Uri Lublin 2019-02-05 17:44:21 UTC
One can redirect stdout/stderr of each remote-viewer instance to a different file, for example:
   remote-viewer --spice-debug console_to_VM1.vv > logVM1 2>&1
   remote-viewer --spice-debug console_to_VM2.vv > logVM2 2>&1

Comment 6 Sandro Bonazzola 2019-03-26 10:14:42 UTC
4.3.1 has been release a while ago as RHV 4.3 Beta 2, re-targeting to 4.3.3 for re-evaluation

Comment 8 Martin Tessun 2019-11-25 08:17:38 UTC
As this seems to be a rare usecase and there is a workaround? See c#5, Closing this RFE.


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