# Time Sync Issue

**URL:** <https://community.ntppool.org/t/time-sync-issue/183>\
**Category:** Server operators\
**Created:** [April 6, 2017, 3:12am UTC](https://community.ntppool.org/t/time-sync-issue/183 "2017-04-06T03:12:53Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![steven](https://avatars.discourse-cdn.com/v4/letter/s/94ad74/32.png) [@steven](https://community.ntppool.org/u/steven)\
**Post date:** [April 6, 2017, 3:12am UTC](https://community.ntppool.org/t/time-sync-issue/183/1 "2017-04-06T03:12:53Z")

</div>

Hello,

Good day to everyone .  
I got time sync issue recently by linux command “/usr/sbin/ntpdate [tw.pool.ntp.org](http://tw.pool.ntp.org)”.  
Here are some details :  
From root@twtpelpssdb01t Wed Apr 5 19:00:02 2017  
Return-Path: [root@twtpelpssdb01t](mailto:root@twtpelpssdb01t)  
Received: from twtpelpssdb01t (localhost [127.0.0.1])  
by twtpelpssdb01t (8.14.4/8.14.4) with ESMTP id v35B02jD030985  
for [root@twtpelpssdb01t](mailto:root@twtpelpssdb01t); Wed, 5 Apr 2017 19:00:02 +0800  
Received: (from root@localhost)  
by twtpelpssdb01t (8.14.4/8.14.4/Submit) id v35B02cc030984;  
Wed, 5 Apr 2017 19:00:02 +0800  
Date: Wed, 5 Apr 2017 19:00:02 +0800  
Message-Id: [201704051100.v35B02cc030984@twtpelpssdb01t](mailto:201704051100.v35B02cc030984@twtpelpssdb01t)  
From: root@twtpelpssdb01t (Cron Daemon)  
To: root@twtpelpssdb01t  
Subject: Cron [root@twtpelpssdb01t](mailto:root@twtpelpssdb01t) /usr/sbin/ntpdate [tw.pool.ntp.org](http://tw.pool.ntp.org)  
Content-Type: text/plain; charset=UTF-8  
Auto-Submitted: auto-generated  
X-Cron-Env: \<SHELL=/bin/sh\>  
X-Cron-Env: \<HOME=/root\>  
X-Cron-Env: \<PATH=/usr/bin:/bin\>  
X-Cron-Env: \<LOGNAME=root\>  
X-Cron-Env: \<USER=root\>

5 Apr 19:00:02 ntpdate[30982]: adjust time server 61.216.153.104 offset -0.006269 sec

From root@twtpelpssdb01t Wed Apr 5 20:00:05 2017  
Return-Path: [root@twtpelpssdb01t](mailto:root@twtpelpssdb01t)  
Received: from twtpelpssdb01t (localhost [127.0.0.1])  
by twtpelpssdb01t (8.14.4/8.14.4) with ESMTP id v35C05t9002988  
for [root@twtpelpssdb01t](mailto:root@twtpelpssdb01t); Wed, 5 Apr 2017 20:00:05 +0800  
Received: (from root@localhost)  
by twtpelpssdb01t (8.14.4/8.14.4/Submit) id v35C05j7002966;  
Wed, 5 Apr 2017 20:00:05 +0800  
Date: Wed, 5 Apr 2017 20:00:05 +0800  
Message-Id: [201704051200.v35C05j7002966@twtpelpssdb01t](mailto:201704051200.v35C05j7002966@twtpelpssdb01t)  
From: root@twtpelpssdb01t (Cron Daemon)  
To: root@twtpelpssdb01t  
Subject: Cron [root@twtpelpssdb01t](mailto:root@twtpelpssdb01t) /usr/sbin/ntpdate [tw.pool.ntp.org](http://tw.pool.ntp.org)  
Content-Type: text/plain; charset=UTF-8  
Auto-Submitted: auto-generated  
X-Cron-Env: \<SHELL=/bin/sh\>  
X-Cron-Env: \<HOME=/root\>  
X-Cron-Env: \<PATH=/usr/bin:/bin\>  
X-Cron-Env: \<LOGNAME=root\>  
X-Cron-Env: \<USER=root\>

**5 Apr 20:00:05 ntpdate[2931]: step time server 61.216.153.105 offset 2678399.804672 sec**

From root@twtpelpssdb01t Wed Apr 5 20:00:09 2017  
Return-Path: [root@twtpelpssdb01t](mailto:root@twtpelpssdb01t)  
Received: from twtpelpssdb01t (localhost [127.0.0.1])  
by twtpelpssdb01t (8.14.4/8.14.4) with ESMTP id v35C09Q2003058  
for [root@twtpelpssdb01t](mailto:root@twtpelpssdb01t); Wed, 5 Apr 2017 20:00:09 +0800  
Received: (from root@localhost)  
by twtpelpssdb01t (8.14.4/8.14.4/Submit) id v35C09uQ003057;  
Wed, 5 Apr 2017 20:00:09 +0800  
Date: Wed, 5 Apr 2017 20:00:09 +0800  
Message-Id: [201704051200.v35C09uQ003057@twtpelpssdb01t](mailto:201704051200.v35C09uQ003057@twtpelpssdb01t)  
From: root@twtpelpssdb01t (Cron Daemon)  
To: root@twtpelpssdb01t  
Subject: Cron [root@twtpelpssdb01t](mailto:root@twtpelpssdb01t) /usr/sbin/ntpdate [tw.pool.ntp.org](http://tw.pool.ntp.org)  
Content-Type: text/plain; charset=UTF-8  
Auto-Submitted: auto-generated  
X-Cron-Env: \<SHELL=/bin/sh\>  
X-Cron-Env: \<HOME=/root\>  
X-Cron-Env: \<PATH=/usr/bin:/bin\>  
X-Cron-Env: \<LOGNAME=root\>  
X-Cron-Env: \<USER=root\>

# 5 Apr 20:00:09 ntpdate[3011]: adjust time server 61.216.153.105 offset -0.000601 sec

Any idea ???

Best Regards,  
Stevenstrong text

---

<div class="post-metadata">

**Author:** ![mengzhuo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/mengzhuo/32/1869_2.png) [@mengzhuo](https://community.ntppool.org/u/mengzhuo)\
**Post date:** [April 6, 2017, 6:03am UTC](https://community.ntppool.org/t/time-sync-issue/183/2 "2017-04-06T06:03:53Z")

</div>

> [@steven](#):
>
> 11]: adjust time server 61.216.153.105 offset -0.000601 sec
> 
> Any idea ???

you shouldn’t use cronjob ntpdate for time adjust, use ntpd instead

---

<div class="post-metadata">

**Author:** ![hildeb](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/hildeb/32/61_2.png) [@hildeb](https://community.ntppool.org/u/hildeb)\
**Post date:** [April 6, 2017, 12:39pm UTC](https://community.ntppool.org/t/time-sync-issue/183/3 "2017-04-06T12:39:34Z")

</div>

Use ntpdate (with multiple servers) ONCE and the start ntpd (also, with multiple servers). ntpdate will make the clock jump backwards, which is a bad thing.

---

<div class="post-metadata">

**Author:** ![alica](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/alica/32/337_2.png) [@alica](https://community.ntppool.org/u/alica)\
**Post date:** [April 6, 2017, 1:42pm UTC](https://community.ntppool.org/t/time-sync-issue/183/4 "2017-04-06T13:42:05Z")

</div>

Sadly there are still some outdated instruction teaching beginners to use cron+ntpdate to keep the time, like the [vbird article](http://linux.vbird.org/linux_server/0440ntp.php#client_linux) (in Chinese).

---

<div class="post-metadata">

**Author:** ![steven](https://avatars.discourse-cdn.com/v4/letter/s/94ad74/32.png) [@steven](https://community.ntppool.org/u/steven)\
**Post date:** [April 6, 2017, 2:38pm UTC](https://community.ntppool.org/t/time-sync-issue/183/5 "2017-04-06T14:38:28Z")

</div>

Actually, we used ntp daemon to sync time for our RAC envs,but still got big differences among RAC nodes. And then we adapted to use ntp command. I am wondering why you said “sad”. Post my comments here is to check anything wrong with the server pools. If you are not the owner, just save your words.

-------- 原始訊息 --------自： CS Chen [ntppool@discoursemail.com](mailto:ntppool@discoursemail.com) 日期： 2017/4/6 21:52 (GMT+08:00) 至： [stevenchang1213@gmail.com](mailto:stevenchang1213@gmail.com) 主旨： [NTP Pool Project] [Server operators] Time Sync Issue

```
          alica
          

          April 6
        
      
    
  

  Sadly there are still some outdated instruction teaching beginners to use cron+ntpdate to keep the time, like the vbird article (in Chinese).

```

Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

---

<div class="post-metadata">

**Author:** ![randy](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/randy/32/53_2.png) [@randy](https://community.ntppool.org/u/randy)\
**Post date:** [April 6, 2017, 4:39pm UTC](https://community.ntppool.org/t/time-sync-issue/183/6 "2017-04-06T16:39:11Z")

</div>

Hi Steven

I am this server operators (61.216.153.104, 61.216.153.105), i don’t know why you has big time differences. if use ntp daemon still has this problem, maybe check your environment first.

my ntp upstream from stdtime.gov.tw

> server tick.stdtime.gov.tw iburst  
> server tock.stdtime.gov.tw iburst  
> server clock.stdtime.gov.tw iburst  
> server watch.stdtime.gov.tw iburst  
> server time.stdtime.gov.tw iburst

**Howto use [pool.ntp.org](http://pool.ntp.org)**  
[pool.ntp.org: 我能如何安装 NTP 以使用NTP池？](http://www.pool.ntp.org/zh/use.html)

---

<div class="post-metadata">

**Author:** ![steven](https://avatars.discourse-cdn.com/v4/letter/s/94ad74/32.png) [@steven](https://community.ntppool.org/u/steven)\
**Post date:** [April 7, 2017, 12:18am UTC](https://community.ntppool.org/t/time-sync-issue/183/7 "2017-04-07T00:18:00Z")

</div>

Roger

從我的 Samsung Galaxy 智慧型手機傳送。  
-------- 原始訊息 --------自： Randy Wong [ntppool@discoursemail.com](mailto:ntppool@discoursemail.com) 日期： 2017/4/7 00:49 (GMT+08:00) 至： [stevenchang1213@gmail.com](mailto:stevenchang1213@gmail.com) 主旨： [NTP Pool Project] [Server operators] Time Sync Issue

```
          randy
          

          April 6

```

Hi Steven

I am this server operators (61.216.153.104, 61.216.153.105), i don’t know why you has big time differences. if use ntp daemon still has this problem, maybe check your environment first.

my ntp upstream from [stdtime.gov.tw](http://stdtime.gov.tw)

server [tick.stdtime.gov.tw](http://tick.stdtime.gov.tw) iburst  
server [tock.stdtime.gov.tw](http://tock.stdtime.gov.tw) iburst  
server [clock.stdtime.gov.tw](http://clock.stdtime.gov.tw) iburst  
server [watch.stdtime.gov.tw](http://watch.stdtime.gov.tw) iburst  
server [time.stdtime.gov.tw](http://time.stdtime.gov.tw) iburst

Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

---

<div class="post-metadata">

**Author:** ![steven](https://avatars.discourse-cdn.com/v4/letter/s/94ad74/32.png) [@steven](https://community.ntppool.org/u/steven)\
**Post date:** [April 7, 2017, 1:58am UTC](https://community.ntppool.org/t/time-sync-issue/183/8 "2017-04-07T01:58:43Z")

</div>

Hello Ralf,

```
            tw.pool.ntp.org is already a server pool .
            Here is my debugging output :

```

[root@twtpelpssdb01t ~]# ntpdate -q [tw.pool.ntp.org](http://tw.pool.ntp.org)  
server 61.216.153.107, stratum 3, offset 0.001884, delay 0.03125  
server 103.18.128.60, stratum 2, offset 0.002737, delay 0.02943  
server 61.216.153.104, stratum 3, offset 0.001884, delay 0.02963  
7 Apr 09:55:02 ntpdate[6302]: adjust time server 103.18.128.60 offset  
0.002737 sec

```
  Anyway thanks for your paying attention on my post.

```

BR,  
Steven

---

<div class="post-metadata">

**Author:** ![steven](https://avatars.discourse-cdn.com/v4/letter/s/94ad74/32.png) [@steven](https://community.ntppool.org/u/steven)\
**Post date:** [April 7, 2017, 2:29am UTC](https://community.ntppool.org/t/time-sync-issue/183/9 "2017-04-07T02:29:23Z")

</div>

Hello mengzhuo [https://community.ntppool.org/users/mengzhuo](https://community.ntppool.org/users/mengzhuo),

```
  I know nptd is a better way to sync time, but sometimes it's not

```

technical issue.  
OK…  
I will use the following command for debugging further.  
/usr/sbin/ntpdate -dB 10.36.15.1 [watch.stdtime.gov.tw](http://watch.stdtime.gov.tw) [tock.stdtime.gov.tw](http://tock.stdtime.gov.tw)  
10.36.1.2  
Actually, I doubt the hardware issue, because only this RAC group got  
probjlems.  
For god sake, I just do my jobs.  
Thanks for your paying attentions.

BR,  
Steven
