From nobody Tue Dec 24 13:24:24 2024 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YHbG21Rkzz5h9Y9 for ; Tue, 24 Dec 2024 13:24:26 +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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YHbG071xBz4rF9 for ; Tue, 24 Dec 2024 13:24:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1735046665; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=hKDOEFrMownuaYezfbahqB1Ap65LpIE2lQqCFtNNUXs=; b=GmEJJDNCo6pQ47U6C/k10KM8MLGHtebCAWX0mavdk5BAh9bROoR7qZ/3D2+/6zwwSv/C38 HY6nl2DMbdndhvRQRPxUdsu2jRqraUPIIZSLw9kbpJEewIVfuycS11De23d/dV6R6024wx Rk+/CWFb5pylbSflFwXpj2ewT85xGgA8+TSrwn39493+n5KNTNjxnXPbM62cagxaYvAHrk BHUlXjLpJXE6cWiP4/Q4fYMYkvkujKdS3v6KVkWpa8bp9usQp4/FhCTgxD4hu9wzfINOr4 +lCbuxsY8jKDBPkxReh9ie8yxymfs7+sUsoYuxQSAZRXV/9hYMrBpW+9V2wFiA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1735046665; a=rsa-sha256; cv=none; b=KQaKtZVpPqHDWt9wvTkB0vhR+9x9M6BYnoS9ONkMmxs5pZkta8UFhyB66iuhWikRY5ig/9 +bTM4Vh72oW78MhpfbQGSOZVadU3T+TWw51RM/qiajhzEfqqz5p4SAj6rRSlqBgcHND0Yl KSAqEVB9CcuR+zhyWwrcbmybyPNqzSWUr4x/cuRSvVwRQnejFyr9BeHfbxwFYBPod2cLYG ANRXGP1Poq+Rwgxj5DqOrpJhQrBNjXYBsZDYXZNFDgHnTByTu2Ve9O60Y5cTXZQyYDz1Aa /3tkDvloxAx+cGD/nJjPn2OZnOXYaZ5YAKVC1Or8EftBfZnfmed+n6LzssU7Jw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YHbG06Dl9zgMv for ; Tue, 24 Dec 2024 13:24:24 +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 4BODOOVX044683 for ; Tue, 24 Dec 2024 13:24:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4BODOOXj044682 for bugs@FreeBSD.org; Tue, 24 Dec 2024 13:24:24 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 283550] freebsd-update doesn't refresh leapsecond file Date: Tue, 24 Dec 2024 13:24:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: 13.4-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: void@f-m.fm X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283550 Bug ID: 283550 Summary: freebsd-update doesn't refresh leapsecond file Product: Base System Version: 13.4-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: conf Assignee: bugs@FreeBSD.org Reporter: void@f-m.fm This issue was encountered on 13.{1,2,3,4}-RELEASE. Other releases not test= ed. A 13.1-p3 amd64 bhyve guest instance needed to be upgraded to latest 13.4. = This was done stepwise, merging files when prompted. The guest instance is an uncomplicated config - a simple web server. The OS has always been maintain= ed with freebsd-update. the path to 13.4-p1 from 13.1-p3 was conducted stepwise latest 13.1 =3D> latest 13.2 =3D> latest 13.3 =3D> latest 13.4 I thought a straight upgrade 13.1 =3D> 13.4 might be too big a jump. I was surprised to find that at each stage in the upgrade, ntpd showed in t= he console at bootup that the leapsecond file was out of date. Example output: Dec 23 16:00:21 REDACTED ntpd[604]: leapsecond file (=E2=80=98/var/db/ntpd.leap-seconds.list=E2=80=99): expired 362 days ago This is from the fully upgraded (so, 13.4-p1) system in /etc/rc.conf there's the following ntp-related settings ntpdate_enable=3D"YES" ntpd_enable=3D"YES" In /etc/defaults/rc.conf there's the following ntpd variables pertaining to leapseconds ntpd_flags=3D"" # Additional flags to ntpd ntp_src_leapfile=3D"/etc/ntp/leap-seconds" # Initial source for ntpd leapfile ntp_db_leapfile=3D"/var/db/ntpd.leap-seconds.list" ntp_leapfile_sources=3D"https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seco= nds.list https://data.iana.org/time-zones/tzdb/leap-seconds.list" ntp_leapfile_fetch_opts=3D"-mq" # Options to use for ntp leapfile fetch, ntp_leapfile_expiry_days=3D30 # Check for new leapfile 30 days prior to ntp_leapfile_fetch_verbose=3D"NO" # Be verbose during NTP leapfile fetch --=20 You are receiving this mail because: You are the assignee for the bug.=