Your message dated Mon, 5 Oct 2026 22:32:07 +0300
with message-id
<capzxpqc5hygwwzdhkxzyrvauan5puev7bt1_vxaxwzv0k1x...@mail.gmail.com>
and subject line Re: openntpd doesn't start anymore
has caused the Debian Bug report #1143621,
regarding openntpd doesn't start anymore
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1143621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1143621
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: openntpd
Version: 1:7.9p1-3
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
I noticed my openntpd wasn't running anymore do to a clock skew error on
building i3 from source. It seems from version 7.9p1-3 and up the location of
the sock file changed from `/var/lib/openntpd/run/ntpd.sock` to
`/run/openntpd/ntpd.sock`. This causes apparmor issues:
Aug 05 02:44:05 sputnik-odin kernel: audit: type=1400
audit(1785912245.478:30553): apparmor="DENIED" operation="mknod" class="file"
profile="/usr/sbin/ntpd" name="/run/openntpd/ntpd.sock" pid=255478 comm="ntpd"
requested_mask="c" denied_mask="c" fsuid=0 ouid=0
Aug 05 02:46:17 sputnik-odin kernel: audit: type=1400
audit(1785912377.102:30562): apparmor="DENIED" operation="mknod" class="file"
profile="/usr/sbin/ntpd" name="/var/lib/openntpd/ntpd.drift" pid=256003
comm="ntpd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
A downgrade to a stable package made it work and while bisecting I noticed the
first error on 1:7.9p1-3, it is also present on 7.9p1-4. Although I didn't test
the openntpd_1%3a6.8p1-6_amd64.deb, openntpd_1%3a6.8p1-5_amd64.deb packages.
To fix the glich I had to add `/run/openntpd/ntpd.sock rw,` to
`/etc/apparmor.d/usr.sbin.ntpd` and reload it with `apparmor_parser -r
/etc/apparmor.d/usr.sbin.ntpd` after which the problem got solved.
Could you please update the apparmor profile for openntpd so issues are
resolved going forward? Many thanks!
Cheers,
Wesley
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (900, 'unstable'), (500, 'testing'), (100, 'experimental'), (10,
'stable-updates'), (10, 'stable-security'), (10, 'oldstable-updates'), (10,
'oldstable-security'), (10, 'oldoldstable'), (10, 'stable'), (10, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 7.1.4+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages openntpd depends on:
ii libc6 2.42-17
ii libtls28t64 3.8.1-2.1+b3
ii netbase 6.5
ii systemd [systemd-sysusers] 261.1-3
openntpd recommends no packages.
Versions of packages openntpd suggests:
ii apparmor 4.1.7-5
-- Configuration Files:
/etc/apparmor.d/usr.sbin.ntpd changed [not included]
/etc/default/openntpd changed [not included]
/etc/openntpd/ntpd.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
ma 5.10.2026 klo 22.22 Wesley Schwengle ([email protected]) kirjoitti:
>
> On 9/15/26 08:02, Martin-Éric Racine wrote:
> >> Sorry, where would you add this? We currently have:
> >>
> >> /usr/sbin/ntpd mrix,
> >> /var/lib/openntpd/ntpd.drift rw,
> >> /run/openntpd/ntpd.sock rw,
>
>
> If you think it is already there and there are no issues, I think the
> bug can be closed. I probably was in some kind of edge case scenario. I duno
Alright. Closing.
Martin-Éric
--- End Message ---
