Hi there
I think some thing wrong with radius plugin's folder structure.
I use nProbe v.8.5.180504 (r6149) , nprobe.conf
with --radius-dump-dir=/milad/radius
while we are at 13:07:41 still files creating in 2018/05/05/12 folder.
as you can see,first file created at 12:31.
same behavior by diameter plugin.
[root@ipdr2 ~]# date
Sat May 5 13:07:41 +0430 2018
[root@ipdr2 ~]# ls /milad/radius/2018/05/05/13
ls: cannot access /milad/radius/2018/05/05/13: No such file or directory
[root@ipdr2 ~]# find /milad/radius/2018/05/05/12 -type f -printf '%T+ %p\n'
| sort | head -1
2018-05-05+12:31:42.0050892550
/milad/radius/2018/05/05/12/radius_zc_ens192f0_1525507241_0.txt
[root@ipdr2 ~]# find /milad/radius/2018/05/05/12 -type f -printf '%T+ %p\n'
| sort | tail -1
2018-05-05+13:08:17.0075408450
/milad/radius/2018/05/05/12/radius_zc_ens192f0_1525509437_36.txt.tmp
[root@ipdr2 ~]# cat /etc/centos-release
CentOS Linux release 7.4.1708 (Core)
I think some thing wrong with radius plugin's folder structure.
I use nProbe v.8.5.180504 (r6149) , nprobe.conf
with --radius-dump-dir=/milad/radius
while we are at 13:07:41 still files creating in 2018/05/05/12 folder.
as you can see,first file created at 12:31.
same behavior by diameter plugin.
[root@ipdr2 ~]# date
Sat May 5 13:07:41 +0430 2018
[root@ipdr2 ~]# ls /milad/radius/2018/05/05/13
ls: cannot access /milad/radius/2018/05/05/13: No such file or directory
[root@ipdr2 ~]# find /milad/radius/2018/05/05/12 -type f -printf '%T+ %p\n'
| sort | head -1
2018-05-05+12:31:42.0050892550
/milad/radius/2018/05/05/12/radius_zc_ens192f0_1525507241_0.txt
[root@ipdr2 ~]# find /milad/radius/2018/05/05/12 -type f -printf '%T+ %p\n'
| sort | tail -1
2018-05-05+13:08:17.0075408450
/milad/radius/2018/05/05/12/radius_zc_ens192f0_1525509437_36.txt.tmp
[root@ipdr2 ~]# cat /etc/centos-release
CentOS Linux release 7.4.1708 (Core)