I'm having trouble tracing the source of this problem, has anyone else
noticed it?  I have fam and libfam0 packages installed as they are
needed by a number of kde packages.  The default configuration for
the xinetd.d/fam is used, and I get page after page of this in my 
log files:

Jul 13 13:13:06 visigoth xinetd[901]: warning: can't get client address: Transport 
endpoint is not connected
Jul 13 13:13:06 visigoth xinetd[901]: libwrap refused connection to sgi_fam from <no 
address>
Jul 13 13:13:06 visigoth xinetd[907]: warning: can't get client address: Transport 
endpoint is not connected
Jul 13 13:13:06 visigoth xinetd[907]: libwrap refused connection to sgi_fam from <no 
address>
Jul 13 13:13:06 visigoth xinetd[912]: warning: can't get client address: Transport 
endpoint is not connected
Jul 13 13:13:06 visigoth xinetd[912]: libwrap refused connection to sgi_fam from <no 
address>
Jul 13 13:13:06 visigoth xinetd[920]: warning: can't get client address: Transport 
endpoint is not connected
Jul 13 13:13:06 visigoth xinetd[920]: libwrap refused connection to sgi_fam from <no 
address>
Jul 13 13:13:06 visigoth xinetd[927]: warning: can't get client address: Transport 
endpoint is not connected
Jul 13 13:13:06 visigoth xinetd[927]: libwrap refused connection to sgi_fam from <no 
address>
Jul 13 13:13:06 visigoth xinetd[932]: warning: can't get client address: Transport 
endpoint is not connected
Jul 13 13:13:06 visigoth xinetd[932]: libwrap refused connection to sgi_fam from <no 
address>
Jul 13 13:13:06 visigoth xinetd[939]: warning: can't get client address: Transport 
endpoint is not connected
Jul 13 13:13:06 visigoth xinetd[939]: libwrap refused connection to sgi_fam from <no 
address>
Jul 13 13:13:06 visigoth xinetd[2097]: Deactivating service sgi_fam due to excessive 
incoming connections.  Restarting in 30 seconds.
Jul 13 13:13:37 visigoth xinetd[2097]: Activating service sgi_fam


There will be groups of this, with about 50 lines of warning/libwrap pairs, then the
notice that xinetd is stopping the sgi_fam service.  There is often a delay of several
hours before the next occurance, but sometimes, it starts as soon as the fam service
is restarted by xinetd.  I am not able to find any correlation.  The first occurrence
of this was on 04 JUL 2002.

versions installed:

kernel-enterprise-2.4.18.21mdk-1-1mdk
fam-2.6.8-2mdk
libfam0-2.6.8-2mdk
iptables-1.2.6a-1mdk
Bastille-1.3.0-2mdk
msec-0.25-1mdk


kdeaddons-3.0.2-1mdk
kdeadmin-3.0.2-1mdk
kdeartwork-3.0.2-1mdk
kdebase-3.0.2-6mdk
kdebase-nsplugins-3.0.2-6mdk
kdeedu-3.0.2-1mdk
kdegames-3.0.2-1mdk
kdegraphics-3.0.2-1mdk
kdelibs-3.0.2-2mdk
kdemultimedia-3.0.2-1mdk
kdemultimedia-aktion-3.0.2-1mdk
kdenetwork-3.0.2-5mdk
kdesdk-3.0.2-1mdk
kdetoys-3.0.2-1mdk
kdeutils-3.0.2-1mdk
krozat-8.3-3mdk



-- 
 +-% He's a real  UNIX Man $-+-------------------------------------+
  \  Sitting in his UNIX LAN  \          Charles A. Shirley         \
   \ Making all his UNIX plans \   cashirley (at) comcast (dot) net  \
    +------# For  nobody @------+-------------------------------------+



Reply via email to