RE: Serious Problem

Robert H. Clugston ( (no email) )
Tue, 26 May 1998 12:25:25 -0700

Dear List,
n EA I had 1800 for the idle-timeout. It was showing as 1800 in radiusNT
debug mode, but it was really 180. Acct termination was idle-timeout. I
finally remove the idle-timeout all together.
This happened after I add a session-timeout to the defaults. Should the
session timeout come before the idle timeout? Would this cause the problem?

-----Original Message-----
[] On Behalf Of Tom Bilan
Sent: Saturday, May 23, 1998 6:04 AM
To: ''
Subject: RE: Serious Problem

First place you want to check is in Emerald Admin under defaults. Find
the service name those people are logging in under and check the
session-timeout value. If there isn't one there and there still being
kicked off then put one there with a value of 30000 which is over 8


> -----Original Message-----
> From: Robert H. Clugston []
> Sent: Friday, May 22, 1998 7:55 PM
> To: Emerald Mailing List
> Subject: Serious Problem
> List,
> I think I sent a message about this problem this morning. The
> majority of
> my users can't connect for more than 5 mins. They are disconnecting
> because
> of idle-timeouts. This started happening last night at 6:00 with no
> changes
> to Emerald.
> I also noticed that my database is full. I have 300 users in a
> 120mB
> database and its full.
> I have had Lucent tech support check out my PM3 and I'm having
> Pacific Bell
> look at the PRI lines.
> Looks like the problem is in Emerald. It looks like its telling
> the user
> there idle timeout is under 10 mins. I'm running radius at the command
> line
> with the -x15 option. Idle-timeout 1800 is being sent to the users.
> Any
> ideas? I'm loosing hair by the hand full ; )