Idle Telnet Timeouts

Not sure if this is the right list to ask this on, too many to choose
from and none of the others looked like what I wanted. Anyway; here's
the deal, I'm running a TinyMUSH world on my system. The problem that
I'm having is that when a player is idle for any length of time they
get disconnected with a "Network error: POSIX error: Operation timed
out" as far as I can tell, this shouldn't be happening. Neither my ISP
nor the MUSH software is disconnecting them. In fact the MUSH has an
idle timeout in it to d/c players that have been idle for too long,
this isn't activating however.

Anyone have any ideas on how I can stop this?

0

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Idle Telnet Timeouts

On Mon, 2007-04-30 at 15:06 -0500, ArcticFox wrote:
> Not sure if this is the right list to ask this on, too many to choose
> from and none of the others looked like what I wanted. Anyway; here's
> the deal, I'm running a TinyMUSH world on my system. The problem that
> I'm having is that when a player is idle for any length of time they
> get disconnected with a "Network error: POSIX error: Operation timed
> out" as far as I can tell, this shouldn't be happening. Neither my ISP
> nor the MUSH software is disconnecting them. In fact the MUSH has an
> idle timeout in it to d/c players that have been idle for too long,
> this isn't activating however.
>
> Anyone have any ideas on how I can stop this?

Any kind of debugging logs? From TinyMUSH or from
syslog/messages/whatever? If not crank up the logging on TinyMUSH.

Are you running DSL using PPPoE?

Any kind of DHCP from your ISP? If your DHCP lease length is short
enough your ISP might inadvertently be disconnecting them during a renew
of you DHCP IP Address.

Are you using port forwarding from any device (a router) to you machine?
Is there a DHCP server running on it causing a blip on your NIC?

IOW, unless you can see some diagnostics from you processes or machines
system logs relating to it... its hard to know.
--
greg,

Novell's Directory Services is a competitive product to Microsoft's
Active Directory in much the same way that the Saturn V is a competitive
product to those dinky little model rockets that kids light off down at
the playfield. -- Thane Walkup

Idle Telnet Timeouts

On Apr 30, 2007, at 5:21 PM, Greg Folkert wrote:

> On Mon, 2007-04-30 at 15:06 -0500, ArcticFox wrote:
>> Not sure if this is the right list to ask this on, too many to choose
>> from and none of the others looked like what I wanted. Anyway; here's
>> the deal, I'm running a TinyMUSH world on my system. The problem that
>> I'm having is that when a player is idle for any length of time they
>> get disconnected with a "Network error: POSIX error: Operation timed
>> out" as far as I can tell, this shouldn't be happening. Neither my ISP
>> nor the MUSH software is disconnecting them. In fact the MUSH has an
>> idle timeout in it to d/c players that have been idle for too long,
>> this isn't activating however.
>>
>> Anyone have any ideas on how I can stop this?
>
> Any kind of debugging logs? From TinyMUSH or from
> syslog/messages/whatever? If not crank up the logging on TinyMUSH.
>
> Are you running DSL using PPPoE?
>
> Any kind of DHCP from your ISP? If your DHCP lease length is short
> enough your ISP might inadvertently be disconnecting them during a
> renew
> of you DHCP IP Address.
>
> Are you using port forwarding from any device (a router) to you
> machine?
> Is there a DHCP server running on it causing a blip on your NIC?
>
> IOW, unless you can see some diagnostics from you processes or machines
> system logs relating to it... its hard to know.
> --
> greg,
>
> Novell's Directory Services is a competitive product to Microsoft's
> Active Directory in much the same way that the Saturn V is a
> competitive
> product to those dinky little model rockets that kids light off down at
> the playfield. -- Thane Walkup
>

The only message in my log for the mush is 'Remote close or net failure'

I'm connected through cable.

My ISP uses DHCP but the lease length is somewhere between a week to a
month.

My router is using port forwarding, the router is also providing the
DHCP services for the local network though the server running the mush
software is set with a static IP.

I'll look and see if there's a way I can increase the logging from
TinyMUSH.

--

Idle Telnet Timeouts

ArcticFox wrote in Article <48e57010d8b5f26fc52860188570261c@insightbb.com>
posted to gmane.linux.debian.user:

> Not sure if this is the right list to ask this on, too many to choose
> from and none of the others looked like what I wanted. Anyway; here's
> the deal, I'm running a TinyMUSH world on my system. The problem that
> I'm having is that when a player is idle for any length of time they
> get disconnected with a "Network error: POSIX error: Operation timed
> out" as far as I can tell, this shouldn't be happening. Neither my ISP
> nor the MUSH software is disconnecting them. In fact the MUSH has an
> idle timeout in it to d/c players that have been idle for too long,
> this isn't activating however.
>
> Anyone have any ideas on how I can stop this?

Sounds like some router between your MUSH and your players is timing out
connections prematurely. Either find and reconfigure the router, or make
sure people use TCP keepalives with relatively short intervals to keep
connections from going stale.

--
Paul Johnson
Email and IM (XMPP & Google Talk):

--

Idle Telnet Timeouts

On Tue, 2007-05-01 at 01:16 -0700, Paul Johnson wrote:
> ArcticFox wrote in Article <48e57010d8b5f26fc52860188570261c@insightbb.com>
> posted to gmane.linux.debian.user:
>
> > Not sure if this is the right list to ask this on, too many to choose
> > from and none of the others looked like what I wanted. Anyway; here's
> > the deal, I'm running a TinyMUSH world on my system. The problem that
> > I'm having is that when a player is idle for any length of time they
> > get disconnected with a "Network error: POSIX error: Operation timed
> > out" as far as I can tell, this shouldn't be happening. Neither my ISP
> > nor the MUSH software is disconnecting them. In fact the MUSH has an
> > idle timeout in it to d/c players that have been idle for too long,
> > this isn't activating however.
> >
> > Anyone have any ideas on how I can stop this?
>
> Sounds like some router between your MUSH and your players is timing out
> connections prematurely. Either find and reconfigure the router, or make
> sure people use TCP keepalives with relatively short intervals to keep
> connections from going stale.

That was exactly the place I was going. I just wanted to see what kind
of errors were being spewed. It could be some settings could be changed
in MUSH. I know that many(some?) MUDs can be tweaked to change these
things.
--
greg,

Novell's Directory Services is a competitive product to Microsoft's
Active Directory in much the same way that the Saturn V is a competitive
product to those dinky little model rockets that kids light off down at
the playfield. -- Thane Walkup

Idle Telnet Timeouts

On May 1, 2007, at 11:42 AM, Greg Folkert wrote:

> On Tue, 2007-05-01 at 01:16 -0700, Paul Johnson wrote:
>> ArcticFox wrote in Article
>> <48e57010d8b5f26fc52860188570261c@insightbb.com>
>> posted to gmane.linux.debian.user:
>>
>>> Not sure if this is the right list to ask this on, too many to choose
>>> from and none of the others looked like what I wanted. Anyway; here's
>>> the deal, I'm running a TinyMUSH world on my system. The problem that
>>> I'm having is that when a player is idle for any length of time they
>>> get disconnected with a "Network error: POSIX error: Operation timed
>>> out" as far as I can tell, this shouldn't be happening. Neither my
>>> ISP
>>> nor the MUSH software is disconnecting them. In fact the MUSH has an
>>> idle timeout in it to d/c players that have been idle for too long,
>>> this isn't activating however.
>>>
>>> Anyone have any ideas on how I can stop this?
>>
>> Sounds like some router between your MUSH and your players is timing
>> out
>> connections prematurely. Either find and reconfigure the router, or
>> make
>> sure people use TCP keepalives with relatively short intervals to keep
>> connections from going stale.
>
> That was exactly the place I was going. I just wanted to see what kind
> of errors were being spewed. It could be some settings could be changed
> in MUSH. I know that many(some?) MUDs can be tweaked to change these
> things.
> --
> greg,
>
> Novell's Directory Services is a competitive product to Microsoft's
> Active Directory in much the same way that the Saturn V is a
> competitive
> product to those dinky little model rockets that kids light off down at
> the playfield. -- Thane Walkup
>

I seem to have fixed it. I adjusted the priority of the port I'm using
for the MUSH software. As of right now I have a character who's been
connected (and idle) for 21 hours and 12 minutes.

Thanks for your suggestions!

--

Syndicate content