Bug 1687628

Summary: [RHEL6] The spice-vdagent is not starting and spice is opening thousands of unix sockets.
Product: Red Hat Enterprise Linux 6 Reporter: Germano Veit Michel <gveitmic>
Component: spice-vdagentAssignee: Default Assignee for SPICE Bugs <rh-spice-bugs>
Status: CLOSED ERRATA QA Contact: SPICE QE bug list <spice-qe-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.10CC: cfergeau, dblechte, fdelorey, fziglio, gveitmic, lsurette, mtessun, pravisha, rduda, rh-spice-bugs, royoung, spice-qe-bugs, tburke, toneata, tpelka, victortoso
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: spice-vdagent-0.14.0-13.el6_10.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1650596 Environment:
Last Closed: 2019-05-14 15:15:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1650596    
Bug Blocks: 1660108    

Comment 9 Radek Duda 2019-04-08 13:53:46 UTC
verified on latest rhel6.10 guest /rhel8 client/host:

[root@localhost test]# netstat -noap | grep spice
unix  2      [ ACC ]     STREAM     LISTENING     13589  2019/spice-vdagentd /var/run/spice-vdagentd/spice-vdagent-sock
unix  2      [ ]         DGRAM                    20207  2478/spice-vdagent  
unix  3      [ ]         STREAM     CONNECTED     15740  2478/spice-vdagent  
unix  3      [ ]         STREAM     CONNECTED     15724  2019/spice-vdagentd /var/run/spice-vdagentd/spice-vdagent-sock
unix  3      [ ]         STREAM     CONNECTED     15712  2478/spice-vdagent  
unix  2      [ ]         DGRAM                    13655  2019/spice-vdagentd 
unix  3      [ ]         STREAM     CONNECTED     13592  2019/spice-vdagentd

Comment 11 errata-xmlrpc 2019-05-14 15:15:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:1227