It claims that there is an accounting packet without an acctsessiontime... I found the offending entries and now it works. I guess I'll have to edit those out each time. They are being created by a web-accelerator program we use.
: Info: [sql] stop packet with zero session length. [user '', nas '69.54.220.130']
This is just an informational message, not an error message, and can be ignored. However, the username for that packet is empty which is probably not what you want.
Once I edit those records out, it works fine. :( offending record looks like:
Wed Dec 29 00:08:22 2010 Event-Timestamp = "Dec 29 2010 00:08:22 EST" User-Name = "<username>" NAS-IP-Address = 69.54.220.130 NAS-Identifier = "TN_GrandRapidsAPX.1dial.com" NAS-Port = 1838 NAS-Port-Type = Async Service-Type = Framed-User Acct-Status-Type = Stop Acct-Delay-Time = 0 Acct-Session-Id = "617355318" Acct-Authentic = RADIUS Acct-Session-Time = 1087 Acct-Input-Octets = 45488 Acct-Output-Octets = 68727 Acct-Input-Packets = 169 Acct-Output-Packets = 155 Acct-Terminate-Cause = Session-Timeout Ascend-Disconnect-Cause = Session-Timeout Ascend-Connect-Progress = LAN-Session-Up Ascend-PreSession-Time = 32 Ascend-Pre-Input-Octets = 347 Ascend-Pre-Output-Octets = 251 Ascend-Pre-Input-Packets = 12 Ascend-Pre-Output-Packets = 12 Ascend-First-Dest = 255.255.255.255 Ascend-Data-Rate = 24000 Ascend-Xmit-Rate = 26400 Ascend-Modem-PortNo = 89 Ascend-Modem-SlotNo = 10 Ascend-Modem-ShelfNo = 1 Calling-Station-Id = "<phone>" Called-Station-Id = "<dialup>" Ascend-Data-Svc = Switched-Voice-Bearer Framed-Protocol = PPP Framed-IP-Address = <ip address> Attr-103 = 0x4d1ac245 Client-IP-Address = <ip address> Acct-Unique-Session-Id = "bcac314c121c56b5" Stripped-User-Name = "<username>" Realm = "<realm>" Timestamp = 1293599302
There's nothing wrong with this packet. It includes the User-Name attribute with a value of "<username>" and the Acct-Session-Time attribute with a value of 1087 seconds. The " Info: [sql] stop packet with zero session length." message would not be generated by this packet. When you leave in the "offending" packets, what happens? Do you just get the "stop packet with zero session length" message? If that's the only "problem", just ignore it or fix the device that is sending that packet. Tim