| Re: [chrony-users] chronyd failing on bootstrap of CIS-hardened AMI, Elastic Beanstalk |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] chronyd failing on bootstrap of CIS-hardened AMI, Elastic Beanstalk
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Wed, 19 Oct 2022 08:46:17 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1666161982; 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:references:references; bh=/UorvlQIrrJzoDBxg1fF8/3hso0nvERC45W3gYWRSuo=; b=AgeIbQdiIVc6QOWSizctpQcMNyRT/PRTcAjVOoEyJAwjnkaESl19oDMCcIcuRVAFXDpTBW 5B6rChoWAEj21XaLfMXOFCCvaoeH62L6ogW81yEgJsdeF/trl6XtTuRd+gusxXIXyEwcDC x///oOV8cnGYUxMCWZpiUnBO9HrW3rg=
On Tue, Oct 18, 2022 at 11:23:26AM -0700, Tom Holub wrote:
> Obviously, this isn't chrony's fault, but I'm looking for advice on how to
> troubleshoot or work around the situation. If I put a User Data directive
> to run chronyd on instance boot, it creates chronyd.pid and chronyd.sock in
> /run/chrony, and the daemon seems to be syncing time, but all of the
> command line commands (like "chronyc sources") return nothing.
Try running "netstate -aenp | grep chronyd" or "ss -anp | grep
chronyd" to see which sockets the process has open. If it's missing a
UDP or Unix domain socket, there should be an error message in the
log. If no socket is missing, it might be a permission problem on the
directory or socket. It could be also be a SELinux/AppArmor issue if
it's enabled on the system. Check /var/log/audit/audit.log if present.
--
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.