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:
Lots of linc socket files are created under '/tmp/orbit-<user>'. This is filling up the inodes in /tmp and creating a problem.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 6.6
ORBit2-2.14.17-5.el6.x86_64

How reproducible:
Always.
'linc-cleanup-sockets' command does clean this, but would like to see a permanent fix.

Steps to Reproduce:
1. Happening on a server with multiple user's logged in (running gnome-session). User's are from ldap using vasd client authentication.
2. On another server, happening only for specific user. 'gnome-session' is launched by '/usr/libexec/nx/nxagent'.

Actual results:
The linc socket files gets accumulated with each login.

Expected results:
The older socket files should get cleared once user logs out from GNOME session.

Problem exists on RHEL6_U8 as well. Same situation where we have users running gnome sessions remotely either through VNC or ExceedOnDemand. 

It is not 100% all of the time, but something happens to the session and the number of orbit sockets that user creates consumes all inodes on the /tmp volume. 

It the case I just cleaned up today it was over 6.8M inodes.
This took the linc-cleanup-sockets about 2 hours to clear on the running system.

Granted it does try to clean up at start now, but if you don't have the devel package installed (we strip as many devel packages from production systems as we can), you get this error now:

gnome-session[1928]: WARNING: Could not launch application 'linc-cleanup-sockets.desktop': Unable to start application: Failed to execute child process "/usr/bin/linc-cleanup-sockets" (No such file or directory)
console.error:

IMO linc-cleanup-sockets should be moved to the main package.