EARLY_CONSENSUS_NOTICE_SKEW of 60 is too strict for some drifting dirauth clocks

I keep getting this error on my relay, I set my timezone as Bucharest, Romania. The relay is running ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-119-generic x86_64) and using Tor 0.3.2.10

[WARN] Received ns flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 1 minutes, 1 seconds, or that theirs is ahead. Tor requires an

  accurate clock to work: please check your time, timezone, and date settings.

17:58:59 [WARN] Our clock is 1 minutes, 1 seconds behind the time published in the consensus network status document (2018-04-09 15:00:00 UTC). Tor needs an accurate clock to

  work correctly. Please check your time and date settings!

Trac:
Username: Dbryrtfbcbhgf