erratic accounting updates after 47 days of uptime
Re: erratic accounting updates after 47 days of uptime
ty,
will do it later on as I'd outage last night and update
thanks
will do it later on as I'd outage last night and update
thanks
Re: erratic accounting updates after 47 days of uptime
state: active
fail count: 0
request count: 0
queue length: 0
auth sent: 57142
auth lost(total/5m/1m): 22/0/0
auth avg query time(5m/1m): 411/376 ms
acct sent: 11726
acct lost(total/5m/1m): 2433/0/0
acct avg query time(5m/1m): 35/23 ms
interim sent: 0
interim lost(total/5m/1m): 0/0/0
interim avg query time(5m/1m): 0/0 ms
again happened plz see the interim sent 0. Its been 25 minutes gone and interval is 600
logs at https://pastebin.com/mf0cqMSL
thanks
fail count: 0
request count: 0
queue length: 0
auth sent: 57142
auth lost(total/5m/1m): 22/0/0
auth avg query time(5m/1m): 411/376 ms
acct sent: 11726
acct lost(total/5m/1m): 2433/0/0
acct avg query time(5m/1m): 35/23 ms
interim sent: 0
interim lost(total/5m/1m): 0/0/0
interim avg query time(5m/1m): 0/0 ms
again happened plz see the interim sent 0. Its been 25 minutes gone and interval is 600
logs at https://pastebin.com/mf0cqMSL
thanks
Re: erratic accounting updates after 47 days of uptime
Hi, do you have defined acct-interim-interval=600 in [radius] radius section? Or can you confirm that radius sends this attribute?
You can join to our telegram international community group https://t.me/accel_ppp_en for fast help.
You can join to our telegram international community group https://t.me/accel_ppp_en for fast help.
Re: erratic accounting updates after 47 days of uptime
hi,
TY,
Its same in radius and accel 600s. Please see the missing updates in graph between 15:00 to 16:00 and reboot around 13:45 hours thanks
TY,
Its same in radius and accel 600s. Please see the missing updates in graph between 15:00 to 16:00 and reboot around 13:45 hours thanks
Re: erratic accounting updates after 47 days of uptime
Can I propose to increase log level and set additional verbose?
Add
After these changes just execute `accel-cmd reload` to apply the configuration.
UPD:/ Provide please `dmesg -T` and journalctl output from 15 to 16
FYI: `interim sent: 0` this is not normal. Is accel-cmd answered when it happened?
Add
Code: Select all
[ppp]
verbose=1
[pppoe]
verbose=1
[radius]
verbose=1
interim-verbose=1
[log]
level=5
log-debug=/var/log/accel-ppp/debug.log
UPD:/ Provide please `dmesg -T` and journalctl output from 15 to 16
FYI: `interim sent: 0` this is not normal. Is accel-cmd answered when it happened?
Re: erratic accounting updates after 47 days of uptime
Hi,
TY,
I'd posted the dmesg output in my other post. Here is the link
https://gofile.io/d/kWlaFI
thanks
TY,
I'd posted the dmesg output in my other post. Here is the link
https://gofile.io/d/kWlaFI
thanks
Re: erratic accounting updates after 47 days of uptime
Community members in our telegram chat recommend disabling SELinux.
Re: erratic accounting updates after 47 days of uptime
hi,
Again interim updates stopped. I'd reduced the log levels as no resolution was coming. It was consuming my disk space. Restarting the services (not accel-cmd) could only resolve the problem. Acce-cmd restart only gave me a stuck service with thousand of finishing connections and nothing active
screenshot
Again interim updates stopped. I'd reduced the log levels as no resolution was coming. It was consuming my disk space. Restarting the services (not accel-cmd) could only resolve the problem. Acce-cmd restart only gave me a stuck service with thousand of finishing connections and nothing active
screenshot
- Attachments
-
- Screenshot from 2020-10-05 23-10-00.png (175.78 KiB) Viewed 4525 times