Hi. This is a follow-up on the error I encountered with AuthBY DYNAADDRESS (shown below). I suspect a bug in the AddressAllocatorSQL.pm starting with the one included in patches-2.17.1. To eliminate the possibility that it is my custom AuthBy module that causes the problem, I tried a simpler config file (attached zip includes both config file and trace 4 log) which is based on the addressallocator.cfg and radmin.cfg supplied in the goodies directory. I do the following test: 1. Startup both primary and secondary MySQL database 2. Start Radiator 3. Attempt authentication using radpwtst -> success 4. Shutdown primary MySQL database 5. Attempt authentication using radpwtst -> failed (same error as below) I also tried Radiator-2.18 and it also failed. What worked is Radiator-2.17.1 using the original AddressAllocatorSQL.pm. I would therefore like to ask regarding the potential race condition the patches.README of patches-2.17.1 described regarding the original module. If my second Radiator server is just a backup and is not used unless the first server timeouts, will we encounter a problem? Thanks. Johann >X-Authentication-Warning: server1.open.com.au: majordomo set sender to >[EMAIL PROTECTED] using -f >X-Sender: [EMAIL PROTECTED] >X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 >Date: Mon, 28 May 2001 08:56:17 +0800 >To: [EMAIL PROTECTED] >From: [EMAIL PROTECTED] (Johann Vincent Paul U. Tagle) >Subject: (RADIATOR) AuthBy DYNADDRESS problem >Sender: [EMAIL PROTECTED] > >Hi. We're using Radiator 2.17.1 with MySQL. I encountered an error using >AuthBy DYNADDRESS: > >The logfile (trace 4) shows: > >Sat May 26 23:58:26 2001: ERR: do failed for 'update RADPOOL set STATE=1, >TIME_STAMP=990892706, >EXPIRY=990919371, USERNAME= where YIADDR='64.94.97.141' and TIME_STAMP >=988339515': You have an error in your SQL syntax near 'where >YIADDR='64.94.97.141' and TIME_STAMP =988339515' at line 2 > >Take note that the USERNAME field does not have any value assigned. The >above repeats so many times and then is followed by: > >Sat May 26 23:58:26 2001: INFO: Access rejected for <username>: Too many >simultaneous address requests > >(I deleted the actual <username> from above) I take it that Radiator >concludes of a too many simultaneous address requests because of the SQL >syntax. This did not happen before when we were in testing phase. Also, >I only had to restart Radiator to fix it. What could have caused the problem? > >Thanks. > >Johann Tagle > >=== >Archive at http://www.open.com.au/archives/radiator/ >Announcements on [EMAIL PROTECTED] >To unsubscribe, email '[EMAIL PROTECTED]' with >'unsubscribe radiator' in the body of the message.
bug in AddressAllocatorSQL.pm Patch? (was Fwd: (RADIATOR) AuthBy DYNADDRESS problem)
Johann Vincent Paul U. Tagle Wed, 30 May 2001 20:31:25 -0700
- bug in AddressAllocatorSQL.pm Patch? (was Fw... Johann Vincent Paul U. Tagle
- bug in AddressAllocatorSQL.pm Patch? (w... Johann Vincent Paul U. Tagle
- Fwd: bug in AddressAllocatorSQL.pm Patc... Johann Vincent Paul U. Tagle