On Nov 7, 2017, at 2:24 PM, Dmitry Yashin via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
Hi, I have a bug in the network and sometimes the stop pack comes before updates. to fix this i write some like this ... but this not work , in debug mode i see
Can you PLEASE NOT USE "radiusd -Xx". Honestly, what is with this? Are the suddenly hundreds of third-party guides recommending this? Why can people not just read the FREERADIUS DOCUMENTATION, and follow it? Why are half of the posts to this list suddenly using "-Xx", after 20 years of "-X" being good enough? And what's with the double-spacing?
Tue Nov 7 21:51:00 2017 : Debug: (222) cache: Mutex acquired
Tue Nov 7 21:51:00 2017 : Debug: (222) cache: No cache entry found for "cc815c1b8cb89841330796a5f48bfa12"
Tue Nov 7 21:51:00 2017 : Debug: (222) cache: Mutex released
Tue Nov 7 21:51:00 2017 : Debug: (222) modsingle[accounting]: returned from cache (rlm_cache)
Tue Nov 7 21:51:00 2017 : Debug: (222) [cache] = notfound
Tue Nov 7 21:51:00 2017 : Debug: (222) } # if (Acct-Status-Type == Interim-Update) = notfound
Tue Nov 7 21:51:00 2017 : Debug: (222) } # accounting = notfound
Tue Nov 7 21:51:00 2017 : Debug: (222) Not sending reply to client.
Tue Nov 7 21:51:00 2017 : Debug: (222) Finished request
why not work if (notfound) in accounting ?
Because the server didn't do anything with the accounting packet. It wasn't stored in the cache, and it wasn't stored anywhere else. You can use module fail-over to control this behaviour: if (Acct-Status-Type == Interim-Update) { update control { Cache-Status-Only = 'yes' } cache { notfound = 1 } ... everything else... That should work. And please, READ THE DOCUMENTATION FOR HOW TO USE DEBUG MODE. It's not hard. Reading all of the extra crap in "-Xx" is getting annoying. If this keeps up, I'm going to just start ignoring EVERY POST which uses the wrong format. Alan DeKok.