Symptom
- ZDATE_ILLEGAL_LOCTIME dumps happen
- ntpd is already configured with the slewing (-x) option (3255206), or chronyd is used
- OS log contain similar entries similar to:
2024-01-30T20:30:02.473068+00:00 hostname <some log>
2024-01-30T20:49:15.060743+00:00 hostname <some log>
2024-01-30T20:48:12.000082+00:00 hostname lsass: [lsass] Failed to sync system time [error code: 40075]
2024-01-30T20:48:24.945079+00:00 hostname SAPSID_01[1234]: AB0 Basis System: Runtime error "ZDATE_ILLEGAL_LOCTIME" occurred.
- with larger time jumps, "Large Timediff" errors can be reported in SAP syslog (also in OS syslog if forwarding is enabled):
Jan 10 10:13:40 hostname SAPSID_01[20051]: A17 Basis System: > Large Timediff DB 1711919090 - Appserver 1730362411 zdate 1812
Jan 10 10:13:40 hostname SAPSID_01[31906]: A17 Basis System: > Large Timediff DB 1711919090 - Appserver 1730362411 zdate 1812
Read more...
Environment
Any Linux distribution and version
Product
Keywords
ntp, ntpd, chrony, chronyd, slewing, ZDATE_ILLEGAL_LOCTIME, lsass, Large Timediff , KBA , BC-OP-LNX , Linux , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.