Multiple accounting requests crash the server

[tnt at kalik.co.yu]

>
>#1:
>
>rad_recv: Accounting-Request packet from host X.X.X.X:46641, id=184,
>length=302
>     User-Name = "blah"
>     NAS-Port = 2
>     NAS-Port-Type = Wireless-802.11
>     NAS-Identifier = "XXXXXX"
>     NAS-IP-Address = X.X.X.X
>     Acct-Status-Type = Stop
>     Calling-Station-Id = "MAC"
>     Called-Station-Id = "MAC"
>     Event-Timestamp = "Jan 25 2008 10:49:13 CET"
>     Acct-Delay-Time = 955
>     Acct-Session-Id = "59fdb3fd"
>     Acct-Authentic = RADIUS
>     Acct-Session-Time = 343
>     Acct-Input-Octets = 48365
>     Acct-Input-Gigawords = 0
>     Acct-Input-Packets = 199
>     Acct-Output-Octets = 42343
>     Acct-Output-Gigawords = 0
>     Acct-Output-Packets = 248
>     Acct-Terminate-Cause = Idle-Timeout
>     Framed-IP-Address = 192.168.51.186
>     WISPr-Location-Name = "Address"
>     Vendor-18529-Attr-42 = 0x484553363333373131
>     Attr-103 = 0x4799b09a
>     Attr-103 = 0x4799b09a
>     WISPr-Location-ID = "isocc=es,cc=34,ac=08080,network=SSID"
>UPDATE query (fails)
>INSERT query (seems to take place)
>rlm_sql (sql): Released sql socket id: 3
>   modcall[accounting]: module "sql" returns ok for request 0
>modcall: leaving group accounting (returns ok) for request 0
>Sending Accounting-Response of id 184 to X.X.X.X port 46641
>Finished request 0
>

Did you find out why did the UPDATE query fail. That's where the trouble
started. INSERT takes much longer to do ...

Ivan Kalik
Kalik Informatika ISP