Hi @Kalradia
It’s still my feeling that something is wrong either with the machine’s RTC, or the internal clock of Netdata, but I’m not sure we can make sure it’s the problem… Please bear with me … ![]()
The error.log reports many is X.XXXXXX secs in the past, and also Postponing alarm checks for 60 seconds, because it seems that the system was just resumed from suspension. which should not normally occur.
Also from your previous paste, the line Offset: +5.495106s is another thing that might point to this.
The hwclock command can also show any drifts with the hardware clock, can you run it for a while with watch hwclock --verbose and check if it shows any Calculated Hardware Clock drift?
Thanks!