Hi team,
I am running ntpd with DCF77 receiver. Ntpd sometimes crash, when signal is bad, but not often. Today I noticed multiple crashes of ntpd and also I have seen my one of my DCF77 clock had bad time. It was some time forward (half hour-hour?).
Later alert from pool.ntp.org monitoring had come, that server is not reachable - but ntpd was running (it have auto-restart). Graph is really strange
You could install Chrony instead, it’s a lot more stable then NTPD.
Your NTP-deamon should not crash, if it does it could be a problem with your hardware.
Or because of your DCF77 receiver, it could be due to overloading of the DCF77 receiver if you have big AM-stations near you.
You could install a band-pass filter to block unwanted signals near you.
AM-stations make a lot of power, and they can easily make your receiver go nuts or take the entire computer down.
When I’m transmitting on 160m (Radio Amateur band) my DCF77 weather-station stops receiving because of receiver overload.
Could be your problem, overloading because of some station near you.
It seems to crash on decoding, usually during some storms nearby.
18 Sep 14:47:38 ntpd[31111]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 38 bits
18 Sep 14:48:00 ntpd[31111]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 21 bits
18 Sep 14:48:56 ntpd[31111]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 56 bits
18 Sep 14:49:00 ntpd[31111]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 3 bits
18 Sep 14:50:00 ntpd[31111]: PARSE receiver #0: FAILED TIMECODE: “-##############RAD-LS-24-124P-24812P12481212412-8112481248P” (check receiver configuration / wiring)
18 Sep 15:22:00 ntpd[31111]: parse: convert_rawdcf: start bit / parity check FAILED for “-----##----#-##–D–S-24–24p1-4812P–481–241–8-1----2–p”
18 Sep 15:22:00 ntpd[31111]: PARSE receiver #0: interval for following error message class is at least 00:01:00
18 Sep 15:22:00 ntpd[31111]: PARSE receiver #0: FAILED TIMECODE: “-----##----#-##–D–S-24–24p1-4812P–481–241–8-1----2–” (check receiver configuration / wiring)
Chrony was not an option - it did not have support for DCF receivers. Now as I am checking, it maybe changed - I have found GitHub - mlichvar/ntp-refclock: Wrapper for ntpd reference clock drivers. I give it a try.
Receiver is “black box” (from ebay), I don’t want to make any hardware hacks.
Anyway thanks for reply, it make I have discover ntp-refclock
