What's new

segmentation fault on ntp

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Kevin K

Regular Contributor
Need help with ntp segmentation faults.
  • GUI reports: "Reminder: The system time has not been synchronized with an NTP server."
  • syslog.log contains many: "reboot_scheduler: [timecheck] NTP sync error"
  • Running "ntp -w -p pool.ntp.org" reports: "Segmentation fault"
  • Running "ntp -w -p 192.81.135.252" reports "ntp: reply from 192.81.135.252..."
  • Running "ntp -w -p go.boom.now" reports "Segmentation fault"
So clearly, ntp doesn't like something about my DNS.

"nslookup pool.ntp.org" reports
Code:
Server:    8.8.8.8
Address 1: 8.8.8.8 dns.google
Name:      pool.ntp.org
Address 1: 45.55.58.103 time.walb.tech
Address 2: 204.2.134.163 pacific.latt.net
Address 3: 129.250.35.250 x.ns.gin.ntt.net
Address 4: 50.18.44.198 smtp.brandonenright.net
or, if I enable "Wan: Use local caching DNS server as system resolver (default: No)" it reports
Code:
Server:    127.0.0.1
Address 1: 127.0.0.1 localhost.localdomain
Name:      pool.ntp.org
Address 1: 129.250.35.251 y.ns.gin.ntt.net
Address 2: 108.62.122.57 ntp2.radio-sunshine.org
Address 3: 99.104.170.138 99-104-170-138.lightspeed.lsvlky.sbcglobal.net
Address 4: 184.105.182.7 ntp3.junkemailfilter.com

but either way, I get segmentation faults when I run "ntp -w -p pool.ntp.org".

If I configure the GUI with an IP address for a time server, it synchs. Suggestions?
 
Need help with ntp segmentation faults.
  • GUI reports: "Reminder: The system time has not been synchronized with an NTP server."
  • syslog.log contains many: "reboot_scheduler: [timecheck] NTP sync error"
  • Running "ntp -w -p pool.ntp.org" reports: "Segmentation fault"
  • Running "ntp -w -p 192.81.135.252" reports "ntp: reply from 192.81.135.252..."
  • Running "ntp -w -p go.boom.now" reports "Segmentation fault"
So clearly, ntp doesn't like something about my DNS.

"nslookup pool.ntp.org" reports
Code:
Server:    8.8.8.8
Address 1: 8.8.8.8 dns.google
Name:      pool.ntp.org
Address 1: 45.55.58.103 time.walb.tech
Address 2: 204.2.134.163 pacific.latt.net
Address 3: 129.250.35.250 x.ns.gin.ntt.net
Address 4: 50.18.44.198 smtp.brandonenright.net
or, if I enable "Wan: Use local caching DNS server as system resolver (default: No)" it reports
Code:
Server:    127.0.0.1
Address 1: 127.0.0.1 localhost.localdomain
Name:      pool.ntp.org
Address 1: 129.250.35.251 y.ns.gin.ntt.net
Address 2: 108.62.122.57 ntp2.radio-sunshine.org
Address 3: 99.104.170.138 99-104-170-138.lightspeed.lsvlky.sbcglobal.net
Address 4: 184.105.182.7 ntp3.junkemailfilter.com

but either way, I get segmentation faults when I run "ntp -w -p pool.ntp.org".

If I configure the GUI with an IP address for a time server, it synchs. Suggestions?

I used IP for a long while, very reliable, unlike my experience using domain names.
Now using Chrony via ntpMerlin, works superbly.
 
Fair question.
AC68U and AC1900
Version 384.19

(And I just added those to my signature but, sadly, I haven't figured out how to make my signature show up here.)
 
Same problem with my router too, Merlin firmware version:386.1, Asus RT-AC88U.

Running "ntp -w -p pool.ntp.org" returns "Segmentation fault"
Running "ntp -w -p 162.159.200.123" returns "ntp: reply from 162.159.200.123: offset...""

Any sustainable solutions other than hardcoding IP address in GUI? ;)
 
Same problem with my router too, Merlin firmware version:386.1, Asus RT-AC88U.

Running "ntp -w -p pool.ntp.org" returns "Segmentation fault"
Running "ntp -w -p 162.159.200.123" returns "ntp: reply from 162.159.200.123: offset...""

Any sustainable solutions other than hardcoding IP address in GUI? ;)
working fine here
octopus@RT-AX86U-EA08:/tmp/home/root# ntp -w -p pool.ntp.org
ntp: reply from 147.78.229.141: offset:+0.005022 delay:0.003862 status:0x24 strat:2 refid:0x94ca3ac2 rootdelay:0.000687 reach:0x01
ntp: reply from 147.78.229.141: offset:+0.005001 delay:0.003983 status:0x24 strat:2 refid:0x94ca3ac2 rootdelay:0.000687 reach:0x03
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top