Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Customer reported over 32K of unix sockets spawned by the spice-vdagent. Noticed that the spice daemon was failing to start also.
Version-Release number of selected component (if applicable):
RHV 4.2.7
The guest is running RHEL 7.4
spice-glib-0.33-6.el7.x86_64
spice-gtk3-0.33-6.el7.x86_64
spice-server-0.12.8-2.el7.1.x86_64
spice-vdagent-0.14.0-14.el7.x86_64
My lab system is running RHEL 7.5 with the latest spice rpms and is also seeing this issue.
How reproducible:
Every time. My lab system is exhibiting the same failures.
Steps to Reproduce:
1. Install a RHEL with spice enabled
2. Login and check the agent and sockets
Actual results:
The spice daemon failed to start and there are about 32K unix sockets belonging to spice-vdagent
Expected results:
Spice daemon should start and there should not be so many sockets.
Additional info:
# netstat -noap | grep spice-vdagent | wc -l
32762
# cat ps| grep spice
root 14801 0.0 0.0 40432 516 ? Ss Nov12 0:04 /usr/bin/spice-vdagent
gdm 28950 0.0 0.0 40432 512 ? Ss Nov12 0:05 /usr/bin/spice-vdagent
unix 2 [ ] STREAM 164308595 28950/spice-vdagent
unix 2 [ ] STREAM 164106007 28950/spice-vdagent
unix 2 [ ] STREAM 164064092 28950/spice-vdagent
unix 2 [ ] STREAM 163985673 28950/spice-vdagent
unix 2 [ ] STREAM 163354789 28950/spice-vdagent
unix 2 [ ] STREAM 163131966 28950/spice-vdagent
unix 2 [ ] STREAM 162613524 28950/spice-vdagent
Lots deleted...
Moving to spice-vdagent in RHEL7 and we might need to clone to RHEL8 too.
Patch that fixes the leak of sockets:
https://lists.freedesktop.org/archives/spice-devel/2018-November/046166.html
The main issue is spice-vdagentd failing to start with "systemd: Job spice-vdagentd.socket/start failed with result 'dependency'.
I wonder if this was fixed by bug 1340160, fix would be in RHEL 7.5 at spice-vdagent-0.14.0-15.el7.x86_64.
Frank, is it possible to test?
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/RHSA-2019:2229