Queue Statistics always showing 0
Hi, I'm trying to get Freeradius statistics but I can see that the Queue statistics are always 0. I tried to add some delay between the Freeradius server and the back-end to force the server to queue the packets and I can see in the log files that the queue is full and can't handle more requests, but still, the statistics show 0 queues, what could be the problem? Freeardius version 3.2.1-1 Mon Jan 23 01:36:19 2023 : Error: !!! ERROR !!! Failed inserting request 586295 into the queue Mon Jan 23 01:36:20 2023 : Error: !!! ERROR !!! Failed inserting request 586296 into the queue Mon Jan 23 01:36:20 2023 : Error: !!! ERROR !!! Failed inserting request 586297 into the queue Mon Jan 23 01:36:20 2023 : Error: !!! ERROR !!! Failed inserting request 586298 into the queue Mon Jan 23 01:36:20 2023 : Error: !!! ERROR !!! Failed inserting request 586299 into the queue Mon Jan 23 01:36:20 2023 : Error: 1 requests have been waiting in the processing queue for 7 seconds. Check that all databases are running properly! Mon Jan 23 01:36:20 2023 : Error: !!! ERROR !!! Failed inserting request 586321 into the queue Mon Jan 23 01:36:20 2023 : Error: !!! ERROR !!! Failed inserting request 586322 into the queue Mon Jan 23 01:36:25 2023 : Error: Received conflicting packet from client vMX1 port 40710 - ID: 33 due to unfinished request in module <queue>. Giving up on old request. [root@localhost dropwatch]# echo "Message-Authenticator = 0x00,FreeRADIUS-Statistics-Type = 19" | radclient -x localhost:18121 status adminsecret Sent Status-Server Id 101 from 0.0.0.0:45296 to 127.0.0.1:18121 length 50 Message-Authenticator = 0x00 FreeRADIUS-Statistics-Type = 19 Received Access-Accept Id 101 from 127.0.0.1:18121 to 127.0.0.1:45296 length 356 FreeRADIUS-Total-Access-Requests = 7 FreeRADIUS-Total-Access-Accepts = 0 FreeRADIUS-Total-Access-Rejects = 0 FreeRADIUS-Total-Access-Challenges = 0 FreeRADIUS-Total-Auth-Responses = 0 FreeRADIUS-Total-Auth-Duplicate-Requests = 0 FreeRADIUS-Total-Auth-Malformed-Requests = 0 FreeRADIUS-Total-Auth-Invalid-Requests = 0 FreeRADIUS-Total-Auth-Dropped-Requests = 0 FreeRADIUS-Total-Auth-Unknown-Types = 0 FreeRADIUS-Total-Auth-Conflicts = 0 FreeRADIUS-Total-Accounting-Requests = 655923 FreeRADIUS-Total-Accounting-Responses = 583903 FreeRADIUS-Total-Acct-Duplicate-Requests = 0 FreeRADIUS-Total-Acct-Malformed-Requests = 0 FreeRADIUS-Total-Acct-Invalid-Requests = 0 FreeRADIUS-Total-Acct-Dropped-Requests = 27543 FreeRADIUS-Total-Acct-Unknown-Types = 0 FreeRADIUS-Total-Acct-Conflicts = 343 FreeRADIUS-Stats-Start-Time = "Jan 23 2023 01:16:33 EST" FreeRADIUS-Stats-HUP-Time = "Jan 23 2023 01:16:33 EST" FreeRADIUS-Queue-Len-Internal = 0 FreeRADIUS-Queue-Len-Proxy = 0 FreeRADIUS-Queue-Len-Auth = 0 * FreeRADIUS-Queue-Len-Acct = 0* FreeRADIUS-Queue-Len-Detail = 0 FreeRADIUS-Queue-PPS-In = 0 FreeRADIUS-Queue-PPS-Out = 0 -- Best regards, Ashraf Al-Basti
On Jan 23, 2023, at 3:24 AM, Ashraf Al-Basti <albasti@gmail.com> wrote:
I'm trying to get Freeradius statistics but I can see that the Queue statistics are always 0.
That's a side effect of moving to the faster atomic queues. It''s more difficult to get accurate stats for the queue length. Plus, the queue starts are generally meaningless. Either everything is OK, and the queue length is zero, or things are going wrong, and the queue is full. There is very very few situations where the queue are partially full. Alan DeKok.
participants (2)
-
Alan DeKok -
Ashraf Al-Basti