ntp offset can't be reduced












0















we have a (windows) ntp server to witch we pull for time service. Connection en rights are oke. When we restart our virtual ubuntu 14.04 server the offset is within 20ms but after 60 sec the offset jumps to over 68000ms.
This is a bit of a problem (understatement) because its a postgres server.



result ntpq -cpe -cas



remote refid st t when poll reach delay offset jitter



10.100.100.4 185.51.192.34 3 u 26 64 377 0.684 69771.3 154.202



+10.100.100.5 10.100.100.4 4 u 29 64 377 0.659 69776.2 166.560



ind assid status conf reach auth condition last_event cnt



1 45921 961a yes yes none sys.peer sys_peer 1



2 45922 942a yes yes none candidate sys_peer 2



connection seems oke.
anyone any idea why the time keeps jumping back to the uge offset?
Or where i can search for the reason why this is happening










share|improve this question























  • did a grep on the syslog after setting date -t manually: Feb 6 13:18:30 lsass: [lsass] Failed to sync system time [error code: 40075] Feb 6 13:18:34 ntpd[7847]: 0.0.0.0 c61c 0c clock_step +69.895747 s Feb 6 13:19:43 ntpd[7847]: 0.0.0.0 c614 04 freq_mode Feb 6 13:19:44 ntpd[7847]: 0.0.0.0 c618 08 no_sys_peer

    – wduizer
    yesterday


















0















we have a (windows) ntp server to witch we pull for time service. Connection en rights are oke. When we restart our virtual ubuntu 14.04 server the offset is within 20ms but after 60 sec the offset jumps to over 68000ms.
This is a bit of a problem (understatement) because its a postgres server.



result ntpq -cpe -cas



remote refid st t when poll reach delay offset jitter



10.100.100.4 185.51.192.34 3 u 26 64 377 0.684 69771.3 154.202



+10.100.100.5 10.100.100.4 4 u 29 64 377 0.659 69776.2 166.560



ind assid status conf reach auth condition last_event cnt



1 45921 961a yes yes none sys.peer sys_peer 1



2 45922 942a yes yes none candidate sys_peer 2



connection seems oke.
anyone any idea why the time keeps jumping back to the uge offset?
Or where i can search for the reason why this is happening










share|improve this question























  • did a grep on the syslog after setting date -t manually: Feb 6 13:18:30 lsass: [lsass] Failed to sync system time [error code: 40075] Feb 6 13:18:34 ntpd[7847]: 0.0.0.0 c61c 0c clock_step +69.895747 s Feb 6 13:19:43 ntpd[7847]: 0.0.0.0 c614 04 freq_mode Feb 6 13:19:44 ntpd[7847]: 0.0.0.0 c618 08 no_sys_peer

    – wduizer
    yesterday
















0












0








0








we have a (windows) ntp server to witch we pull for time service. Connection en rights are oke. When we restart our virtual ubuntu 14.04 server the offset is within 20ms but after 60 sec the offset jumps to over 68000ms.
This is a bit of a problem (understatement) because its a postgres server.



result ntpq -cpe -cas



remote refid st t when poll reach delay offset jitter



10.100.100.4 185.51.192.34 3 u 26 64 377 0.684 69771.3 154.202



+10.100.100.5 10.100.100.4 4 u 29 64 377 0.659 69776.2 166.560



ind assid status conf reach auth condition last_event cnt



1 45921 961a yes yes none sys.peer sys_peer 1



2 45922 942a yes yes none candidate sys_peer 2



connection seems oke.
anyone any idea why the time keeps jumping back to the uge offset?
Or where i can search for the reason why this is happening










share|improve this question














we have a (windows) ntp server to witch we pull for time service. Connection en rights are oke. When we restart our virtual ubuntu 14.04 server the offset is within 20ms but after 60 sec the offset jumps to over 68000ms.
This is a bit of a problem (understatement) because its a postgres server.



result ntpq -cpe -cas



remote refid st t when poll reach delay offset jitter



10.100.100.4 185.51.192.34 3 u 26 64 377 0.684 69771.3 154.202



+10.100.100.5 10.100.100.4 4 u 29 64 377 0.659 69776.2 166.560



ind assid status conf reach auth condition last_event cnt



1 45921 961a yes yes none sys.peer sys_peer 1



2 45922 942a yes yes none candidate sys_peer 2



connection seems oke.
anyone any idea why the time keeps jumping back to the uge offset?
Or where i can search for the reason why this is happening







networking server ntp






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked yesterday









wduizerwduizer

34117




34117













  • did a grep on the syslog after setting date -t manually: Feb 6 13:18:30 lsass: [lsass] Failed to sync system time [error code: 40075] Feb 6 13:18:34 ntpd[7847]: 0.0.0.0 c61c 0c clock_step +69.895747 s Feb 6 13:19:43 ntpd[7847]: 0.0.0.0 c614 04 freq_mode Feb 6 13:19:44 ntpd[7847]: 0.0.0.0 c618 08 no_sys_peer

    – wduizer
    yesterday





















  • did a grep on the syslog after setting date -t manually: Feb 6 13:18:30 lsass: [lsass] Failed to sync system time [error code: 40075] Feb 6 13:18:34 ntpd[7847]: 0.0.0.0 c61c 0c clock_step +69.895747 s Feb 6 13:19:43 ntpd[7847]: 0.0.0.0 c614 04 freq_mode Feb 6 13:19:44 ntpd[7847]: 0.0.0.0 c618 08 no_sys_peer

    – wduizer
    yesterday



















did a grep on the syslog after setting date -t manually: Feb 6 13:18:30 lsass: [lsass] Failed to sync system time [error code: 40075] Feb 6 13:18:34 ntpd[7847]: 0.0.0.0 c61c 0c clock_step +69.895747 s Feb 6 13:19:43 ntpd[7847]: 0.0.0.0 c614 04 freq_mode Feb 6 13:19:44 ntpd[7847]: 0.0.0.0 c618 08 no_sys_peer

– wduizer
yesterday







did a grep on the syslog after setting date -t manually: Feb 6 13:18:30 lsass: [lsass] Failed to sync system time [error code: 40075] Feb 6 13:18:34 ntpd[7847]: 0.0.0.0 c61c 0c clock_step +69.895747 s Feb 6 13:19:43 ntpd[7847]: 0.0.0.0 c614 04 freq_mode Feb 6 13:19:44 ntpd[7847]: 0.0.0.0 c618 08 no_sys_peer

– wduizer
yesterday












0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1116060%2fntp-offset-cant-be-reduced%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1116060%2fntp-offset-cant-be-reduced%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Category:香港粉麵

List *all* the tuples!

Channel [V]