From owner-freebsd-bugs@freebsd.org Mon Nov 25 21:08:13 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D14831BA337 for ; Mon, 25 Nov 2019 21:08:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 47MKPn3p2Jz3wxf for ; Mon, 25 Nov 2019 21:08:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 8254F1BA334; Mon, 25 Nov 2019 21:08:13 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 821911BA333 for ; Mon, 25 Nov 2019 21:08:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47MKPn2wKTz3wxd for ; Mon, 25 Nov 2019 21:08:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 473CF1A925 for ; Mon, 25 Nov 2019 21:08:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id xAPL8Duo069968 for ; Mon, 25 Nov 2019 21:08:13 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id xAPL8DEh069955 for bugs@FreeBSD.org; Mon, 25 Nov 2019 21:08:13 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 242137] [NTP] "Unexpected origin timestamp 0xe180e455.d15bf3fb does not match aorg 0000000000.00000000 from server" (kernel reports TIME_ERROR: 0x41: Clock Unsynchronized) Date: Mon, 25 Nov 2019 21:08:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 12.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: cy@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: cy@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2019 21:08:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242137 Cy Schubert changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |cy@FreeBSD.org CC| |cy@FreeBSD.org --- Comment #15 from Cy Schubert --- Read this carefully. There are a number of outputs being requested here. Your network or upstream has issues. Compare offset and jitter of the server that has the error with the server that does not. You've only been able to reach once (or 7 times). Compere this with those that work. Can we have output of cat /var/db/ntp/ntp.drift please? Large drift in conjunction with the inability to contact each ntp sever is the cause of th= is error. You should see synchronization flags (*, #, +, -) in your ntpq output. We s= ee none. You're not synchronizing. Again, this points to probable problems with either your local network, upstream, or denied by your firewall. ---- Try adding rlimit memlock 32 to ntp.conf. (This will not work with ASLR enabled.) This was the only change to ntp prior to r354367. (With ASLR enab= led, mlock() caused a segfault and stack corruption.) How much RAM is installed on this machaine? How much swap is configured? How much swap is in use? ---- Please answer all of the questions above. Again: 1. Can you ping your ntp servers? What is the round trip time? 2. Is UDP/123 open? 3. What is in ntp.drift? 4. How much RAM is in the machine? 5. Is swap being used and is ntpd using some of that swap? 6. Does setting memlock in ntp.conf do anything for you? --=20 You are receiving this mail because: You are the assignee for the bug.=