Knowledge Doc: System time not correct, causing issues on server reboots

Heather Caldwell OpenText Employee

0 Likes

4 months ago

Environment

Open Enterprise Server

Situation

The server has issues after it reboots - on startup, the timestamps in /var/log/messages appear to be 6 hours ahead. After the server bootup completes, NTP eventually sets the time back to the correct time. When this occurs, /var/log/messages becomes flooded with these alerts:

/opt/novell/ganglia/monitor/sbin/gmetad[1764]: RRD_update (/var/opt/novell/ganglia/rrds/__SummaryInfo__/mem_shared.rrd): /var/opt/novell/ganglia/rrds/__SummaryInfo__/mem_shared.rrd: illegal attempt to update using time 1718984640 when last update time is 1719006073 (minimum one second step)

Cause

The Hardware Clock does not match the System Clock

Read full article

Labels:

Support Tips/Knowledge Docs

Comment List

Georg H. Weber 4 months ago

Please adjust the TID according to the OES version. OES 2023 uses chronyd as time service. systemctl list-units | grep -i ntp --- > chronyd.service loaded active running NTP client/servery

Another thing is timekeeping in connection when PowerSave is used in virtualization. Keyword Constant Time Stamp Counter (TSC),
cat /proc/cpuinfo | grep constant_tsc ---> flags constant_tsc can cause similar problems when rebooting in the case of powersaving.

Anyway, it's my view of things and it may be nonsense here

George

“You can't teach a person anything, you can only help them to discover it within themselves.” Galileo Galilei
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel

Recommended

Menu

Open Enterprise Server Tips

Knowledge Doc: System time not correct, causing issues on server reboots

Environment

Situation

Cause

Labels:

Resources