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.
Bug 857016 - Orbit2 causes connection failures on heavily loaded systems
Summary: Orbit2 causes connection failures on heavily loaded systems
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ORBit2
Version: 6.4
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Dan Winship
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 863735 866469
TreeView+ depends on / blocked
 
Reported: 2012-09-13 11:50 UTC by Parthasarathi Susarla
Modified: 2018-11-29 20:45 UTC (History)
7 users (show)

Fixed In Version: ORBit2-2.14.17-3.2.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-14 10:38:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 662623 0 None None None 2012-09-13 11:50:40 UTC

Description Parthasarathi Susarla 2012-09-13 11:50:40 UTC 
Description of problem:
GConfd-2 clients fail to connect to the gconfd under heavy load. This leads to various error messages on the console.

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


How reproducible:
Recursively spawning gnome-terminals is a sure shot way to reproduce this issue.


Steps to Reproduce:
1.
2.
3.
  
Actual results:

Errors like the one below:

Failed to summon the GConf demon; exiting.  Failed to contact
configuration server; some
possible causes are that you need to enable TCP/IP networking for
ORBit, or you have stale
NFS locks due to a system crash. See http://projects.gnome.org/gconf/
for information.
(Details -  1: Could not send message to GConf daemon: Message did
not receive a reply
(timeout by message bus))

and:


Failed to summon the GConf demon; exiting.  Failed to contact
configuration server; some
possible causes are that you need to enable TCP/IP networking for
ORBit, or you have stale
NFS locks due to a system crash. See http://projects.gnome.org/gconf/
for information.
(Details -  1: Ping to server error
IDL:omg.org/CORBA/COMM_FAILURE:1.0・・




Expected results:
No Error

Additional info:

* There is a gconfd instance listening to incoming connections
* The gnome-terminals keep spawning and talk to gconfd over ORbit2 sockets
* At some point in time, there is a contention from one of the gnome-terminal instance for a socket file, when it tries to make a connection:

 connect(12, {sa_family=AF_FILE, path="/tmp/orbit-partha/linc-146f-0-6730f10292203"}, 46) = -1 EAGAIN (Resource temporarily unavailable)

* gnome-terminal tries to connect once again, and when it fails this time around, it bails out with the error message that you see printed on screen.

This bug has been fixed in el5: https://bugzilla.redhat.com/show_bug.cgi?id=694451 and has been approved upstream (https://bugzilla.gnome.org/show_bug.cgi?id=662623)
Comment 2 Dan Winship 2012-09-13 14:17:23 UTC 
we already have a patch for this, on bug 694451 (against RHEL5, but it would apply to RHEL6 too)
Comment 5 Siddharth Sharma 2012-09-25 09:03:54 UTC 
As per comment 4 seems from the case that customer wanted z stream but can we get it fixed in rhel-6.4 or make it in Z stream
Comment 7 RHEL Program Management 2012-10-09 11:38:13 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 8 RHEL Program Management 2012-10-12 17:09:44 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Note You need to log in before you can comment on or make changes to this bug.