| Re: [chrony-dev] Multihomed (multiple) network interfaces support ! |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] Multihomed (multiple) network interfaces support !
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 12 Dec 2023 13:22:57 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1702383780; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=io3bTWQxGp44Oy1BEgHrVdtulLND4Q5xtNs0lonZuJ4=; b=RDqdNno5LCIStgoS+QHTYmjDxuM5zJ55HX0yYC08ZU0wTkGQEvubV1jxR+Xh8WFPew7cdC vAtz3cvyfWqgG3WM7tamY62jec0sFbVcw8ZOqSOjb8DElfK4whsSbKHMwLhRcyrCtLVgQH KM+fu0Ud05c3GmgkPhpDse4R8fX6G5c=
On Mon, Dec 11, 2023 at 06:04:18PM +0300, CpServiceSPb wrote:
> Which ports will be listened to, 123 ?
> I mean by server from clients in ln/dmz ?
Yes, 123.
> I did such a configuration.
>
> Launched as chronyd -d ang got:
> Could not add source 127.0.0.1
That would indicate you have the same source specified multiple times
in the config. Try the configs I posted. They have only one source
specified.
> If I launched via multi script I got:
> Starting server instance #1
> Starting server instance #2
> Starting server instance #3
> Starting server instance #4
> Starting client instance
> Fatal error : Another chronyd may already be running (pid=135687), check
> /var/run/chrony/chronyd-server2.pid
That suggests there is an unexpected chronyd instance running on the
system, maybe from a previous test which wasn't terminated properly?
See what process has the PID 135687.
Maybe your system is cursed and cannot run chrony as expected.
Try ntpsec. It should be easier to configure for your requirements.
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.