Bug #2918
closedntpd doesn't sync if not bound to any interface
0%
Description
When no interfaces are selected under Services=>NTP, in attempt to use NTP only for timekeeping on the server itself, ntpd does not successfully sync with the time server.
ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
tyldum.com .INIT. 16 - - 64 0 0.000 0.000 0.000
This command was run 24 hours after ntpd was started - it's definitely not going to sync.
Selecting one or more interfaces to listen to, and it looks like this after 10 minutes:
ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*tyldum.com 192.38.7.240 2 u 1 64 1 53.866 22.635 15.528
Updated by Renato Botelho over 11 years ago
- Status changed from New to Rejected
I tried to reproduce on 3 different installations without success, ntpd worked as expected selecting one, more than one or no interface. Please use the forum to discuss/diagnose and back to bug tracker if it's a confirmed bug.