Description of problem:
When remotely opening an ssh shell from a client to an RHEL AS3 server
and launching a graphical application (e.g. gedit), gedit never
displays on the clients' desktop ; the server /var/log/messages shows
lots of :
Jan 26 16:57:57 dmbr063 xinetd: libwrap refused connection to
sgi_fam (libwrap=fam) from <no address>
Jan 26 16:57:58 dmbr063 xinetd: warning: can't get client
address: Transport endpoint is not connected
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. % ssh remote_server
2. % gedit
Nothing happens on the client side ; the server /var/log/messages is
swamped with errors (see above).
server gedit session should show up on client desktop.
- This looks like the same behaviour as bug #74696 ;
- adding "flags = NOLIBWRAP" to /etc/xinet.d/sgi_fam circumvents the
- This behaviour only occurs on one of our three RHEL AS3 servers; all
servers have comparable /etc/hosts.* tcpwrappers settings.
I am getting the same error messages on a fresh install of RHEL WS 3.0
(with patches) when I try to login at the GUI console login (Gnome,
KDE, and failsafe all do it). The screen stays on the blue background
and the disk goes nuts as the error messages are sent many times per
second to /var/log/messages.
This is a slower machine (P3@600MHz with 512MB) so maybe a faster
system eventually gets the GUI started. The only way I could login
though, was to put "fam: ALL" in tcp wrappers, or to stop xinetd
entirely, or to disable tcp wrappers.
This strikes me as an important bug to be fixed. :-)
This also occurs on one of my FC1 boxes :
This is a duplicate of bug #108582. This bug seems to be in Fedora
Core 1 Test 3, Fedora Core 1 and RHEL 3. Can someone mark this as a
I made a typing error in comment #3. This bug is a duplicate of #108583.
An errata has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
This issue isn't really fixed by the package provided in errata xinetd-2.3.12-6.3E
As described in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119918#c2
it is fixed since version xinetd-2.3.13-1. Would ever a backport or a minor
release update be supplied for RHEL3?