Re: PM2e-30/ComOS-3.3.2: telnet refused, dialup unreliable -- memory leak?

Bruce Komito (brucek@sierra.net)
Sat, 21 Dec 1996 09:47:45 -0800 (PST)

We've had this problem for two years and continue to have it. If you
routinely telnet into your PM, plan on rebooting it every 3-4 weeks as a
precaution. On the other hand, if you leave it alone, it will run for
months.

On Sat, 21 Dec 1996, Chris Shenton wrote:

> I installed a PM2e-30 with ComOS-3.3.2 at a customer's site a few
> months ago, and it operated fine for a couple months. It's got about
> 20 modems on it.
>
> Now, after running for about 90 days, it's having serious problems:
>
> * it's refusing telnet connections so the admin can't talk to it
> (UNIX telnet says "connection refused"; no daemon on that port)
>
> * they report that all the users are having problems dialing in --
> only about one out of five times do they get a valid PPP login.
>
> These problems didn't happen earlier, so I am suspecting a memory
> leak.
>
> Fortunately, I *was* able to get in via FreeBSD + pmcommand, and they
> were able to get in via Win pmconsole. We would be screwed if this was
> hosed like telnet. :-(
>
> They rebooted it, and found that they could then get in via telnet,
> users were able dial-in and get PPP-connected quickly, as before.
>
>
> Any one else had this problem? Is this a known bug in 3.3.2? Should I
> upgrade to 3.3.3 (or wait for 3.3.5)?
>
> (The customer site is 8000 miles away, so my access to the box is
> rather limited)-:
>
>
>