This bug was fixed in the package chrony - 3.5-6ubuntu6.1
---
chrony (3.5-6ubuntu6.1) focal; urgency=medium
* d/patches/: Add allow-some-*time64-syscalls-in-seccomp-filter.patch
(LP: #1878005) Thanks to Vincent Blut
- backport time64 fix to 3.5-6 level
-- Christian
Tests fixed, Verified - this is ready for Focal other than the aging
period that needs to pass.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878005
Title:
Chrony crashes on install from raspberry
FYI: The armhf test is known to be flaky, improved in groovy and retried
in Bionic for this SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878005
Title:
Chrony crashes on install from
Trying as-is on armhf:
After install I see the reported fail:
$ systemctl status chrony
● chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor
preset: enabled)
Active: failed (Result: protocol) since Wed 2020-05-27 08:40:07
Hello Jason, or anyone else affected,
Accepted chrony into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/chrony/3.5-6ubuntu6.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Migrated in Groovy, uploaded to Focal-unapproved waiting on the SRU Team
now.
** Changed in: chrony (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package chrony - 3.5-9ubuntu1
---
chrony (3.5-9ubuntu1) groovy; urgency=medium
* Merge with Debian unstable (LP: #1878005). Remaining changes:
- d/chrony.conf: use ubuntu ntp pool and server (LP 1744664 1754358)
- Set -x as default if unable to set
FYI: Merge of 3.6-9 uploaded to Groovy
** Description changed:
[Impact]
- * Chrony can't start on platorms that map gettimeofday to
-clock_gettime64()
+ * Chrony can't start on platforms that map gettimeofday to
+ clock_gettime64()
- * This is due to syscall filtering being
@Christian - You won't encounter this problem on 64-bit architectures.
These *time64 system calls are dedicated to 32-bit ones to make them
Y2038-compatible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/384238
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878005
Title:
Chrony crashes on
MP to merge 3.5-9 in Groovy
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/384237
MP to fix this in Focal:
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/384238
** Changed in: chrony (Ubuntu Focal)
Status: Confirmed => Triaged
FYI - /me is trying an armhf image later on because that is the likely
place to hit this ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878005
Title:
Chrony crashes on install from raspberry pi
Yep, I'll merge 3.5-9 now which will also give me the test improvements that I
recently submitted to you. The tests still keep failing sometimes, so that will
help as well.
Once that is good in groovy I'll go for the SRU on top of 3.5-6ubuntu6.
@Vincent - have you found a clear reproducer for
chrony 3.5-9 now lands in Debian unstable with a fix (let’s hope) for this
issue.
The patch might need to be refreshed to apply cleanly on top of chrony
3.5-6ubuntu6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Upstream the changes got applied, I expect that Debian gets a related
upload soon'ish and will then merge it for Groovy - SRUs will then start
from there.
** Changed in: chrony (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
FYI - the upstream discussion on the details of the patch still goes on
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878005
Title:
Chrony crashes on install from raspberry pi 2
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chrony (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878005
Found it - Upstream discussion at:
https://www.mail-archive.com/chrony-dev@chrony.tuxfamily.org/msg02161.html
Needs a minor rework to compile on older platforms (that miss
clock_gettime64), but otherwise seems good.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thank you @Vincent - when you have a patch/link/commit let me know so I
can tack the discussion and help doing merging the chrony upload into
Groovy and an SRU into Focal.
I have already done some preliminary SRU paperwork on the bug
description.
** Description changed:
+ [Impact]
+
+ *
Works for me as well. Thank you very much Vincent!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878005
Title:
Chrony crashes on install from raspberry pi 2
To manage notifications about this bug
Seems I was a bit slow on the upload, but the oneliner works on my end
as expected and chrony works as expected after a reboot. Thanks for the
help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you Robert.
So we will need to whitelist the clock_gettime64() system call in chronyd’s
seccomp filter.
I’ll send a patch upstream.
Meanwhile, you can disable the seccomp filter by running (as root):
# sed -i '/DAEMON_OPTS=/s/"-F -1"/"-F 0"/' /etc/default/chrony
# systemctl restart
Hi all and no worries. I'm just glad to help where I can. See attachment
for chronyd_debug.log
** Attachment added: "chronyd_debug.log"
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1878005/+attachment/5371065/+files/chronyd_debug.log
--
You received this bug notification because
execve("/usr/sbin/chronyd", ["chronyd", "-d", "-F", "-1"], 0xbe9ae644 /* 24
vars */) = 0
brk(NULL) = 0x20e5000
uname({sysname="Linux", nodename="dc2", ...}) = 0
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb6ff8000
Hey folks,
Sorry for my silence, I’m terribly busy lately…
Could you please install strace and run:
# strace -o /tmp/chronyd_debug.log chronyd -d -F -1
Then attach the output file (/tmp/chronyd_debug.log).
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
root@ubuntu:/home/ubuntu# chronyd -d -d
2020-04-01T17:26:07Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC
+PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG)
2020-04-01T17:26:07Z Frequency -126.137 +/- 90.667 ppm read from
/var/lib/chrony/chrony.drift
2020-04-01T17:26:15Z
root@ubuntu:/home/ubuntu# bash -x /usr/lib/systemd/scripts/chronyd-starter.sh
-d -F -1
+ set -ue
+ CONF=/etc/default/chrony
+ DOC=/usr/share/doc/chrony/README.container
+ CAP=cap_sys_time
+ CMD=/usr/sbin/chronyd
+ EFFECTIVE_DAEMON_OPTS='-d -F -1'
+ '[' -f /etc/default/chrony ']'
+ .
Hmm,
so chrony-pid doesn't exist and was properly cleaned up for you - odd.
But then starting the daemon seems to just work (no errors) yet then we
get no running process.
We need to switch on more debug, would you mind running this:
$ bash -x /usr/lib/systemd/scripts/chronyd-starter.sh -d -F
ubuntu@ubuntu:~$ systemctl status chrony
chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset>
Active: failed (Result: protocol) since Wed 2020-04-01 17:24:19 UTC; 6min >
Docs: man:chronyd(8)
root@dc2:/etc/chrony# chronyd -d -d
2020-05-13T13:13:47Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC
+PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG)
2020-05-13T13:13:47Z Frequency -2.286 +/- 1.012 ppm read from
/var/lib/chrony/chrony.drift
2020-05-13T13:13:52Z Selected
root@dc2:/etc/chrony# systemctl status chrony
● chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor
preset: enabled)
Active: failed (Result: protocol) since Wed 2020-05-13 15:07:23 CEST; 21s
ago
Docs: man:chronyd(8)
The "protocol" exit is seen a few times in regard to stricter PID handling, for
example:
-
https://unix.stackexchange.com/questions/493187/systemd-under-ubuntu-18-04-1-fails-with-failed-to-create-user-slice-serv
- https://github.com/systemd/systemd/issues/8085
Chrony sets:
>From the log:
chrony.service: New main PID 1224 does not exist or is a zombie.
chrony.service: Failed with result 'protocol'.
I've had focal's chrony running on Pi3 and Pi4 systems without trouble -
I wonder what that is about.
--
You received this bug notification because you are a member of
Same problem. Chrony starts without problems using "chronyd -d -d" as
root.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878005
Title:
Chrony crashes on install from raspberry pi 2
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chrony (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878005
Title:
See attached file for systemctl status output
** Attachment added: "output of systemctl status chrony.service"
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1878005/+attachment/5369985/+files/chrony.service.output
--
You received this bug notification because you are a member of
Hi Jason,
Could you please show us the output of 'systemctl status
chrony.service'?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878005
Title:
Chrony crashes on install from raspberry pi 2
To
37 matches
Mail list logo
