These log messages refer to the TIMESYNC (Firewall time synchronization events) category.
2.75.1. synced_clock (ID: 03500001)
- Default Severity
- NOTICE
- Log Message
- The clock at <oldtime>, was off by <clockdrift> second(s) and synchronized with <timeserver> to <newtime>
- Explanation
- The clock has been synchronized with the time server.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 2
- Parameters
- oldtime
newtime
clockdrift
timeserver
2.75.2. failure_communicate_with_timeservers (ID: 03500002)
- Default Severity
- WARNING
- Log Message
- Communication with the timeserver(s) failed. Clock not updated.
- Explanation
- The unit failed to establish a connection with the time sync server. The clock has not been updated.
- Firewall Action
- clock_not_synced
- Recommended Action
- Verify that the time sync server is running.
- Revision
- 1
2.75.3. clockdrift_too_high (ID: 03500003)
- Default Severity
- WARNING
- Log Message
- According to the timeserver the clock has drifted <clockdrift> seconds(s) which is NOT in the allowed correction interval
(+/-<interval> seconds)
- Explanation
- The clock has drifted so much that it is not within the allowed +/- correction interval. The clock will not be updated.
- Firewall Action
- clock_not_synced
- Recommended Action
- If the correction interval is too narrow, it can be changed in the DateTime section.
- Revision
- 2
- Parameters
- clockdrift
timeserver
interval
2.75.4. no_drift (ID: 03500004)
- Default Severity
- NOTICE
- Log Message
- Correction within range, no update.
- Explanation
- Drift below one second, no update.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 2
2.75.5. ha_synced_clock (ID: 03500005)
- Default Severity
- NOTICE
- Log Message
- Synchronized time with HA peer. Old time: <oldtime>, New time: <newtime>, Drift:<clockdrift> second(s).
- Explanation
- The clock has been synchronized with the HA active node.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 1
- Parameters
- oldtime
newtime
clockdrift
2.75.6. dst_changed (ID: 03500006)
- Default Severity
- NOTICE
- Log Message
- DST is changed to <dst>. System time is <time> <tzlocation> <tzoffset>
- Explanation
- Daylight Saving Time (DST) has been changed.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 2
- Parameters
- dst
time
tzlocation
tzoffset
2.75.7. tzlocation_changed (ID: 03500007)
- Default Severity
- NOTICE
- Log Message
- Timezone location has been changed from <oldlocation> to <newlocation> <time> <tzoffset>
- Explanation
- Timezone location has been changed.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 2
- Parameters
- oldlocation
newlocation
time
tzoffset
2.75.8. leaving_daylight_saving (ID: 03500010)
- Default Severity
- NOTICE
- Log Message
- Leaving Daylight saving time and switching to non-DST time zone.
- Explanation
- Automatic DST is activated and time is adjusted by the system.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 2
- Parameters
- dstoffset
nondstoffset
2.75.9. entering_daylight_saving (ID: 03500011)
- Default Severity
- NOTICE
- Log Message
- Leaving standart time zone and switching to Daylight saving time.
- Explanation
- Automatic DST is activated and time is adjusted by the system.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 2
- Parameters
- dstoffset
nondstoffset
2.75.10. dst_location_not_found (ID: 03500012)
- Default Severity
- ERROR
- Log Message
- Timezone could not be loaded from database.
- Explanation
- Required data for the chosen location could not be found in time zone database.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 2
- Parameters
- location
2.75.11. ntp_auth_error (ID: 03500020)
- Default Severity
- WARNING
- Log Message
- Communication with timeserver <name> on IP address <timeserver> failed due to authentication error <errorcode>.
- Explanation
- Communication with timeserver failed due to authentication error. The NTP packet was dropped.
- Firewall Action
- drop
- Recommended Action
- Verify that the TimeSyncServer is correctly configured and that both sides use the same NTP Authentication key.
- Revision
- 1
- Parameters
- name
timeserver
errorcode
2.75.12. ntp_pkt_error (ID: 03500021)
- Default Severity
- WARNING
- Log Message
- Packet from timeserver <name> on IP address <timeserver> was dropped due to validation error <errorcode>.
- Explanation
- NTP Packet was dropped due to validation error.
- Firewall Action
- drop
- Recommended Action
- None
- Revision
- 1
- Parameters
- name
timeserver
errorcode
2.75.13. ntp_timeout (ID: 03500022)
- Default Severity
- WARNING
- Log Message
- Failed to contact timeserver <name> on IP address <ip_address>. Retried <retries> times. Authentication <authentication>.
- Explanation
- Failed to contact timeserver.
- Firewall Action
- None
- Recommended Action
- Verify that the TimeSyncServer can be reached and that both sides use the same NTP Authentication key if authentication is
enabled.
- Revision
- 1
- Parameters
- name
ip_address
authentication
retries
cOS Core 15.00.04 Log Reference Guide
