Re: Questions with Radius

Dale E. Reed Jr. ( (no email) )
Fri, 28 Aug 1998 22:42:18 -0700

Dusan Janjic wrote:
> > > mode. Here are the error messages from the log file:
> > >
> > ...
> > > I am not sure how to solve this??
> >
> > Run the rad25_up2.sql script against your Emerald database. It includes
> > the missings fields noted.
> This seemed to fix the problem but only partially. I have noticed more then
> usual number of users that Radius reports as logged in. Here is the portion of
> the messages from the log file:
> Fri Aug 28 13:45:42 1998: ODBC Error:23000:547:
> [Microsoft][ODBC SQL Server Driver][SQL Server]INSERT statement conflicted
> with COLUMN FOREIGN KEY constraint 'FK__RadLogs__RadLogM__1E1A7EA3'. The
> conflict occurred in database 'Emerald', table 'RadLogMsgs', column
> 'RadLogMsgID'

The other common issue is that you don't have any entries in the
RadLogMsgs table. Because of constraints, you can't put an entry into
the RadLogs table w/out a defining entry in the RadLogMsgs table.
Run these lines in isql_w to populate the table:

INSERT RadLogMsgs VALUES(0, "Generic Message", 0)
INSERT RadLogMsgs VALUES(1, "Generic Error", 5)

INSERT RadLogMsgs VALUES(10, "User Not Found", 3)
INSERT RadLogMsgs VALUES(11, "Bad Password", 3)
INSERT RadLogMsgs VALUES(12, "User Expired", 2)
INSERT RadLogMsgs VALUES(13, "User OverDue", 2)
INSERT RadLogMsgs VALUES(14, "Over Login Limit", 1)
INSERT RadLogMsgs VALUES(15, "No Time Left", 1)
INSERT RadLogMsgs VALUES(16, "Port Not Allowed", 2)
INSERT RadLogMsgs VALUES(19, "No Attributes", 3)

INSERT RadLogMsgs VALUES(50, "Bad Request", 4)
INSERT RadLogMsgs VALUES(51, "No Username", 4)
INSERT RadLogMsgs VALUES(52, "No Password", 4)
INSERT RadLogMsgs VALUES(53, "Bad Digest", 6)
INSERT RadLogMsgs VALUES(54, "Bad username", 3)

INSERT RadLogMsgs VALUES(60, "Parse Error", 5)
INSERT RadLogMsgs VALUES(100, "Chap Not Allowed", 5)

> Fri Aug 28 13:45:56 1998: User: rockplan already logged onto system 1 time(s).

Is the callsonline looking correct? This could be a result of
accounting problems and callsonline not be right.

> It seems that either, Radius doesn't send the proper string to Emerald to
> inform it of the termination of the session, or (unlikely ) unusual high
> number of our users is trying to log in twice.

Most likely you have an accounting problem that is preventing the
callsonline from being accurate. That could be a result of a full
database, errant accounting, etc.

-- Dale E. Reed Jr.  (       IEA Software, Inc.      |  RadiusNT, Emerald, and NT FAQs Internet Solutions for Today  |