My 2TB MyCloud doesn’t have “ntpd” running on it. In fact, it doesn’t even have an executable for “ntpd”.
Interestingly, it does *initially* synchronize time with the Linux machine on my LAN if I add the entry “192.168.1.3” to the server pool (here’s the line from /etc/ default/ntpdate ) :
More interestingly, while there is no “ntpd” there *are* “/usr/sbin/ntpdate” and “/usr/sbin/ntpdate-debian”, which does
appear to be getting started by “init”. But it seems like what it does is sync the time - successfully - with the server on 192.168.1.3, and then exits without starting any sort of “Daemon” on the MyCloud.
I discovered this when the time on the MyCloud wandered out of sync, and I successfully ran “invoke-rc.d ntpdate start” andit *did* resynchronize… But there’s still no obvious *Daemon* running, and I can only assume it will probably wander out of sync again (which, for anyone who doesn’t know why I’m obsessed with this, is a Bad Thing if you’re using a system as a backup server as I am.)
here are some lines from /var/log/daemon.log :
Jul 12 23:56:13 WDMyCloud ntpdate: Can’t find host time.windows.com: Name or service not known (-2)
Jul 12 23:56:53 WDMyCloud ntpdate: Can’t find host pool.ntp.org: Name or service not known (-2)
Jul 12 23:54:07 WDMyCloud ntpdate: step time server 192.168.1.3 offset -172.228438 sec
The MyCloud can’t reach the Internet from inside my LAN (deliberately), so no surprise on the other two servers.
Meanwhile… trolling around on the net turns up the fact that “ntpdate” is deprecated *and* that “ntpd” has been in Debian as far back as I can remember (and “ntpdate” has not - in fact I think it’s a USB program?) …
So, before I go on a massive debugging binge, I thought I’d ask if anyone here knew about this… is there supposed to be a time server running on the MyCloud, and what is its name, and why is WD using the (supposedly deprecated) “ntpdate”, and - most importantly - why am I not getting periodic time sychronization? … Etc…