Thread-topic: [chrony-users] Porting to Ubuntu 18.04 from 16.04
Thank you!
Disabling the apparmor profile for chrony has fixed it.
-------- Original message --------
From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date: 10/21/19 7:34 AM (GMT-05:00)
To: chrony-users@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [chrony-users] Porting to Ubuntu 18.04 from 16.04
On Tue, Oct 15, 2019 at 07:43:24PM +0000, Knaup, Jacob wrote:
> Oct 15 15:41:51 autorally4 chronyd[2733]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS +IPV6 -DEBUG)
> Oct 15 15:41:51 autorally4 audit[2733]: AVC apparmor="DENIED" operation="mknod" profile="" name="/tmp/chrony.arGPSroverPortB.sock" pid=2733 comm="chronyd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
> Oct 15 15:41:51 autorally4 chronyd-starter.sh[2727]: bind() failed
> Oct 15 15:41:51 autorally4 chronyd[2733]: Fatal error : bind() failed
It looks like AppArmor is too restrictive here. Also, there is a
difference between the path in the config file and in the log.
/tmp/chrony.arGPSroverPortB.sock
vs
/var/run/chrony.arGPSroverPortB.sock
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.