Pual and Hugh,
We initially have the same problem as Hugh described; i.e., a
situation with duplicate NAS-Identifier + NAS-port. The way to get around
is to generate a session id based on NAS-Identifier + NAS-port +
DATE:HH24-MI-SS. This should guarantee uniqueness unless you get
multiple
Hi All,
We are using Radiator 3.6 with latest patches but we are seeing an issue
when a new session is added. We're getting Duplicate key which appears to be
coming from the internal handler code rather than MySQL itself. Below is the
error when it occurs. We've modified our delete from RADONLINE
, Inc.
Tel: 888-460-2286 ext 202
Fax: 866-627-8808
Email: [EMAIL PROTECTED]
**
- Original Message -
From: Paul [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, July 24, 2003 6:49 PM
Subject: (RADIATOR) Issue with Duplicate Key when Adding a Session
[EMAIL PROTECTED]
To: Paul [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, July 25, 2003 1:07 PM
Subject: Re: (RADIATOR) Issue with Duplicate Key when Adding a Session
I would recommend using an INSERT IGNORE instead of an INSERT.
This is a mysql issue, it means that you have a unique key
Message -
From: Brian Morris [EMAIL PROTECTED]
To: Brandon [EMAIL PROTECTED]; Paul [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, July 24, 2003 8:29 PM
Subject: Re: (RADIATOR) Issue with Duplicate Key when Adding a Session
Hmm... What are the implications of an Insert Ignore
Hello Paul -
The error is a MySQL error which is complaining about a duplicate entry
for a unique key.
The unique key for the RADONLINE table is the combination of the
NAS-Identifier and NAS-Port which is what Radiator bases its session
database and simultaneous use checking on - the
