OPNSense 23.1.5 - NTP service fails

Started by guest34985, March 29, 2023, 05:16:08 PM

Previous topic - Next topic
Hi everyone,

after the update to 23.1.5 NTP service fails to start (even after second reboot). Logfiles has this:

2023-03-29T17:14:08 Error ntpd daemon child exited with code 1
2023-03-29T17:14:08 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING


Used to work flawlessly before, maybe you have a hint ...

BR

Having same issue since this morning's update.

Same issue here. Log file looks indentical.

Had the same issue...

I saw running NTP processes listening on the selected interfaces but looks like on initial boot maybe the service checker didn't align?

I was able to force kill the PIDS from the command line and restart NTP from the web UI and its reflected properly now.

Same. Ran top, existing ntpd process was running ("couldn't bind to wildcard address" when starting?), killed it, service started right up.
OPNsense 24.7.7  - QEMU/KVM (Ubuntu), i9-9900K 16 core @ 5ghz, 16GB RAM, 64GB SSD, 2 dedicated SFP+ NICs

# opnsense-patch 4ac3e1d57368

Looks like this is the bad commit.


Cheers,
Franco

The patch fixed it, ntpd starts again after reboot.

Thx!

March 29, 2023, 10:28:35 PM #7 Last Edit: March 29, 2023, 11:40:40 PM by MikeH
Can confirm the patch works. After applying the patch, NTP instantly works.
Also no errors in log after restarting the service.

Thx