(RADIATOR) RADUSAGE table corrupt..deleted, now getting SQL Timeout for new Access Requests.

[Michael Bellears]

Our Radusage Table became corrupt, so I deleted all data with: DELETE
FROM RADUSAGE;

Stopped both Radiator+MySQL, and restarted both, now Accounting Requests
are being inserted into SQL, but access requests are getting time outs:


*** Received from 203.149.65.3 port 2403 ....
Code:       Access-Request
Identifier: 129
Authentic:  <140>&<222><186>H<8>%<27><175><141>N[<161>l<12>[
Attributes:
        User-Name = "tester"
        User-Password =
"i<171>v<192><131><162>_<163>z<19><210>,<130><174><202>{"
        NAS-IP-Address = 203.149.65.3

Wed Nov 17 21:56:06 2004: DEBUG: Rewrote user name to tester
Wed Nov 17 21:56:06 2004: DEBUG: Rewrote user name to tester
Wed Nov 17 21:56:06 2004: DEBUG: Handling request with Handler
'Realm=DEFAULT'
Wed Nov 17 21:56:06 2004: DEBUG:  Deleting session for tester,
203.149.65.3, 
Wed Nov 17 21:56:06 2004: DEBUG: do query is: delete from RADONLINE
where NASIDENTIFIER='203.149.65.3' and NASPORT=

Wed Nov 17 21:57:06 2004: ERR: do failed for 'delete from RADONLINE
where NASIDENTIFIER='203.149.65.3' and NASPORT=': SQL Timeout

Radiator 3.5, Radmin 1.7.

Regards,
MB

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.