I interpret the error message to mean that the exception occurred in the library libc to which chronyd was linked dynamically, so the fault may or may not be caused by chronyd.
Did your error occur during initialization of chrony or after it had run for a while? What type of CPU does your machine have? How much memory? What version of TC are you using? What other extensions are loaded?
If I execute MC on a kvm virtual machine
kvm -cdrom microcore_3.6.iso
and boot using
microcore syslog
and execute
tce-load -wi chrony
grep chronyd /var/log/messages
so chrony is the only extension loaded, I get
Jun 4 16:55:45 (none) daemon.info chronyd[528]: chronyd version 1.24 starting
Jun 4 16:55:46 (none) daemon.info chronyd[528]: Initial txc.tick=10000 txc.freq=0 (0.00000000) txc.offset=0 => hz=100 shift_hz=7
Jun 4 16:55:46 (none) daemon.info chronyd[528]: set_config_hz=0 hz=100 shift_hz=7 basic_freq_scale=1.28000000 nominal_tick=10000 slew_delta_tick=833 max_tick_bias=1000
Jun 4 16:55:46 (none) daemon.info chronyd[528]: Linux kernel major=2 minor=6 patch=33
Jun 4 16:55:46 (none) daemon.info chronyd[528]: calculated_freq_scale=1.00000000 freq_scale=1.00000000
Jun 4 16:55:46 (none) daemon.err chronyd[528]: Could not open IPv6 NTP socket : Address family not supported by protocol
Jun 4 16:55:46 (none) daemon.err chronyd[528]: Could not open IPv6 command socket : Address family not supported by protocol
Jun 4 16:55:46 (none) daemon.info chronyd[528]: System's initial offset : 0.841167 seconds slow of true (slew)
Jun 4 16:55:59 (none) daemon.info chronyd[528]: Selected source 72.26.125.125
which shows that chrony has been started successfully.
If you cannot get chrony to work, you can try ntpclient in a cron job.