Incoming Packet information do not modify the Accounting Table
Hello guys, I recently installed freeradius server. I am only using the accounting mechanism of the system for keeping logs. I am monitoring the server for a week now and today I face with a problem that couldnt solve. The problem is that, in the "detail" log of the client, I can see the incoming STOP packets of a specific session_id and the cause of termination is stated as "Idle-timeout". In general when these packets arrive to the server, it goes and closes the active session of a user in the accounting table stating that the connection of a user disconnected at a given time. But sometimes, some STOP packets with Idle-Timeout cause, do not run the necessary query in the radius for updating the accounting table for that session. This do not happens always. But I need to find the solution for that. I want to see that every LOG inside the "detail" log of a NAS client, should be proceed by the radius for the necessary changes. Like I said, some times, some packets inside the detail log is like ignored by the radius for updating the accounting table. What can be the reason of this situation? I can only think may be it is because of the heavy loads of traffic at that time in terms of packets arriving to the radius from NAS. I only have 1 client and the radiusd.conf is set to default values. What is the solution Guys? Thank you in advance. -- View this message in context: http://freeradius.1045715.n5.nabble.com/Incoming-Packet-information-do-not-m... Sent from the FreeRadius - User mailing list archive at Nabble.com.
How can I read the debug output? Server is not running with "-X" parameter. How can I re-play the packets? -- View this message in context: http://freeradius.1045715.n5.nabble.com/Incoming-Packet-information-do-not-m... Sent from the FreeRadius - User mailing list archive at Nabble.com.
yagizozen wrote:
How can I read the debug output? Server is not running with "-X" parameter.
Read what I wrote: Set up a test server.
How can I re-play the packets?
$ man radclient It's only hard if you REFUSE to read the answers on this list, and if you REFUSE to read the existing documentation. Alan DeKok.
Thank you for your answer Alan. I understand how to re-play the packets using radclient but I wonder if it is possible to see the debug output of an existing running radius server with "radiusd" command without stopping it. -- View this message in context: http://freeradius.1045715.n5.nabble.com/Incoming-Packet-information-do-not-m... Sent from the FreeRadius - User mailing list archive at Nabble.com.
On Thu, Apr 26, 2012 at 5:54 PM, yagizozen <yagizozen@yahoo.com> wrote:
Thank you for your answer Alan. I understand how to re-play the packets using radclient but I wonder if it is possible to see the debug output of an existing running radius server with "radiusd" command without stopping it.
Try using radmin to activate and log debug mode selectively: http://freeradius.org/radiusd/man/radmin.html You need to make sure sites-available/control-socket is enabled (i.e. symlinked in sites-enabled), possibly edit some things there to make it work. Also last time I tried (which is about two years ago) some output might be different compared to when running radiusd -X (e.g. attributes in incoming packets were not printed), so radiusd -X on a test server is definitely still the best option to accurately debug problems. -- Fajar
So this means that the best way to keep detailed debug log, I need to stop the server and start it in debug mode I guess. The only thing that makes me to worry is that when I redirect the output of the command "radiusd -X" to a text file by using ">", it will generate a huge text file in a day. -- View this message in context: http://freeradius.1045715.n5.nabble.com/Incoming-Packet-information-do-not-m... Sent from the FreeRadius - User mailing list archive at Nabble.com.
yagizozen wrote:
So this means that the best way to keep detailed debug log, I need to stop the server and start it in debug mode I guess.
That's wrong. You were told it's wrong. You were told what to do. If you're not going to read the answers on this list, then don't ask questions here.
The only thing that makes me to worry is that when I redirect the output of the command "radiusd -X" to a text file by using ">", it will generate a huge text file in a day.
That's wrong, too. You were told what to do. You're ignoring our advice. Go do what you were told to do. Don't post any more questions until you've done that. Alan DeKok.
yagizozen wrote:
Thank you for your answer Alan. I understand how to re-play the packets using radclient but I wonder if it is possible to see the debug output of an existing running radius server with "radiusd" command without stopping it.
$ man raddebug This is documented. Alan DeKok.
participants (3)
-
Alan DeKok -
Fajar A. Nugraha -
yagizozen