You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unexpected behaviour (obvious or verified by project member)
How can the issue be reproduced?
Hello,
When we input the value field for Expiration in the radcheck table using the date format 2025-01-27 10:00:00, the date is not being validated. We attempted to update the date module with the format format = "%Y-%m-%dT%H:%M:%S", but the issue persists. How can we resolve this to use the specified date format correctly?
Thank you!
Log output from the FreeRADIUS daemon
(121) sql: ERROR: Error parsing value: failed to parse time string "2025-02-01 15:15:00"
(121) sql: ERROR: Error parsing user data from database result
(121) sql: ERROR: Error getting check attributes
Relevant log output from client utilities
No response
Backtrace from LLDB or GDB
The text was updated successfully, but these errors were encountered:
What type of defect/bug is this?
Unexpected behaviour (obvious or verified by project member)
How can the issue be reproduced?
Hello,
When we input the value field for Expiration in the radcheck table using the date format 2025-01-27 10:00:00, the date is not being validated. We attempted to update the date module with the format format = "%Y-%m-%dT%H:%M:%S", but the issue persists. How can we resolve this to use the specified date format correctly?
Thank you!
Log output from the FreeRADIUS daemon
Relevant log output from client utilities
No response
Backtrace from LLDB or GDB
The text was updated successfully, but these errors were encountered: