[chrony-users] chrony didnt start with fudge entry in the conf |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-users] chrony didnt start with fudge entry in the conf
- From: Henry Rolofs <henry.rolofs@xxxxxxxxxxx>
- Date: Wed, 4 Jan 2023 16:39:42 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vodafone.de; s=vfde-mb-mr2-21dec; t=1672846790; bh=cwz6Wc1j0WCb1qDbGeFLw29So6Zrnrliy5sPW4GsByA=; h=Message-ID:Date:User-Agent:To:From:Subject:Content-Type:From; b=EojlwyDzqqpHKboMchSUdfKZODoKZzRLg+Mz+gU5+uyQ2t1rWz8MwBTgyTKIq5UFc XIzptfFlg3koeWoSI2ZIkuZLXIYMLAIUdNAwPPEu9pfBUsZ+AA3c8++gIbHBjcNqmI 5kL4z18Y+JICDVLvODoMe6p6D9BF2nPSIxLfRzEE=
Hello together,
I try to use the local clock with chrony. I added this both line to the
conf.
server 127.127.1.0
fudge 127.127.1.0 stratum 12
With this entries in the conf file (special the fudge entry) chrony
don't start and i got this error
Jan 04 16:25:14 nuc systemd[1]: Starting chrony, an NTP client/server...
Jan 04 16:25:14 nuc chronyd[2147294]: chronyd version 4.2 starting
(+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS
+SECHASH +IPV6>
Jan 04 16:25:14 nuc chronyd[2147294]: Fatal error : Invalid directive at
line 2 in file /etc/chrony/conf.d/local.conf
Jan 04 16:25:14 nuc chronyd-starter.sh[2147292]: Invalid directive at
line 2 in file /etc/chrony/conf.d/local.conf
Jan 04 16:25:14 nuc systemd[1]: chrony.service: Control process exited,
code=exited, status=1/FAILURE
Jan 04 16:25:14 nuc systemd[1]: chrony.service: Failed with result
'exit-code'.
Jan 04 16:25:14 nuc systemd[1]: Failed to start chrony, an NTP
client/server.
This happens with chrony 4.2 that comes with ubuntu 22.04 and also with
a compiles chrony directly from the git sources.
Regrds, Henry
--
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.