I have a customer running D3 on Red Hat Linux 7.1. Every once and a while,
new telnet sessions cannot be opened on the system. When you try to connect,
the message below displays but no login is ever received. Existing telnet
sessions are not affected and neither are the serial connections. If you
close a telnet session and try to re-connect, the same thing happens.

Red Hat Linux release 7.1 (Seawolf)
Kernel 2.4.2-2smp on a 2-processor i686


The only solution I am aware of is a reboot. Has anyone else encountered
this behavior and what remedy have you found?

Thanks,
Jeff

--
Jeffrey Kaufman
Key Data Systems Group
www.keydata.us
559-432-3832
559-432-4657 fax

Western Pacific Supply
www.westpacsupply.com
888-WestPac

I know nothing about D3 on RH but have had a similar problem on other
platforms where the system runs out of tcp/ip connections... In my case,
this was caused by a faulty network card which was causing tcpip connections
to get left open...

Don't know if its related, or any help at all..

Regards
Simon
"Jeffrey Kaufman" <jkaufman (AT) keydata (DOT) us> wrote

Confirming Simons findings, network card CAN have an impact - one of
the worst used to be Broadcom (still may be, but we use Intel).

May be a sledge hammer & a wallnut, but may consider an upgrade to D3
7.4/RH9 - not a supported platform for >12 months now, but being
"later" may help

Linux gurus may have more insight (tuneables, use 'top' to find
zombies etc), but NOT being an expert I'd get to a later release first
.....

(That said, we DO have people on 7.2.1/RH7.1, but aren't seeing this
problem .... using Intel ethernet cards with IBM servers though)

Jeffrey Kaufman wrote:

Are the *nix processes still holding the port?
ps -ef|grep *port*

Is it there in LISTU?

Does the linux appear in a !netstat

Patrick, <;=)

Jeffrey Kaufman wrote:
Hi Jeffrey,

I have not seen RH7.1 for a while, but I think RH7.1 used xinetd rather
than the old inetd super server.

If your system is running xinetd, check out /etc/xinetd.conf. This
config file holds global settings for xinetd, the line of interest is
'instances = 60', which is the default setting. Increase the number of
instances, restart xinetd (service xinetd restart) and this should fix
your problem.

HTH

Barry

Thanks for the suggestion Patrick, but when this happens and the customer
calls me, I have no way to get on the system. I will have to try this next
time by talking the user through it.
Jeff

"Patrick Latimer" <"Patrick Latimer"> wrote

Thanks for the suggestion.

They are floating telnet ports. There are about 100 available for a 20 user
system.

<bgraetz (AT) bigpond (DOT) net.au> wrote

Whoa! I've given up on this kind of support. We don't provide any support
unless we can access their machine. We __NEVER__ try to walk anyone through
something on the phone!

You're a better man than I. :-)

Bill

"Jeffrey Kaufman" <jkaufman (AT) keydata (DOT) us> wrote

Jeffry:

Do you get a bunch of connections listed when you do a "netstat -a | grep
telnet". This should tell us how many telnet connections are "established";
which, if they are, could explain why linux is hitting the "instances"
limitation in "/etc/xinetd.conf". Floating or non-floating telnet ports, I
think, would have no bearing on this question.

Bill

"Jeffrey Kaufman" <jkaufman (AT) keydata (DOT) us> wrote