Error in browser: Clock discrepancy detected. Attempting re-sync

help
1

Hello everyone,

I am getting this error A LOT (to the tune of 1000 logs per 24h on Kadira). It doesn’t seem to be affecting anything, but it is still worrying me. I cannot find anything about it on Google. Does anyone have an idea what might be causing this and how to get rid of it? We are hosted on Modulus.

1 Like
2

Likely from mizzao_timesync.js which is included when you add the mizzao:user-status package.

1 Like
3

+1 same issue 20char

4

See the explanation here.

5

How to solve this???

6

I guess it is hacky, but I simply added the
mizzao:timesync

package and then set

TimeSync.loggingEnabled = false;
7

Where to set on sever/client /lib

8

You set it on the client

9

Thank you for providing some statistics on that re-sync trigger for my package.

May I ask how many users you have over 24 hours to generate 1000 log messages? Maybe I should make that re-sync threshold more generous.

10

Around 20 concurrent users most of the time

11

Actually, that error probably comes up most of the time due to entering and exiting standby. So it doesn’t have much to do with how many active users there are. Anyway. thanks for the info.

2 Likes
12 
setInterval(function(){
// ALT TAB ALTTAB
	if( TimeSync.isSynced() == false){
		//alert("Timesync out of range, refreshing (this will go away soon)");
		location.reload();
	}
},3000);

At least she will refresh now – I kinda hate it but it keeps the user connected.