radius audit log timestamp is restored to 0000

inverse-inc / packetfence

PacketFence is a fully supported, trusted, Free and Open Source network access control (NAC) solution. Boasting an impressive feature set including a captive-portal for registration and remediation, centralized wired and wireless management, powerful BYOD management options, 802.1X support, layer-2 isolation of problematic devices; PacketFence can be used to effectively secure networks small to very large heterogeneous networks.

https://packetfence.org

GNU General Public License v2.0

1.39k stars 291 forks source link

radius audit log timestamp is restored to 0000 #8314

Closed JeGoi closed 2 months ago

JeGoi commented 2 months ago

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

Go to to see a radius entry
See the year cleaned to 0000

Screenshots

Expected behavior Having the real date.

Additional context Zammitbug related

satkunas commented 2 months ago

ALTER TABLE radius_audit_log MODIFY created_at TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP;

Shahzaib-Akhtar-khan commented 1 week ago

hi i have same issue i am working on clustering when i sync the time of all 3 servers i get audit log issue as i didnt see new add device and the time stamp is also incorrect

JeGoi commented 1 week ago

@Shahzaib-Akhtar-khan Please, could you add your Packetfence version? Thank you