Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NTP does not work H.1.2 #414

Closed
royito55 opened this issue Jun 28, 2023 · 5 comments
Closed

NTP does not work H.1.2 #414

royito55 opened this issue Jun 28, 2023 · 5 comments

Comments

@royito55
Copy link

royito55 commented Jun 28, 2023

  • There is no way to sync the create3 to an NPT server or whatever the default configuration is in there.

  • I've seen it work 2 out of 200 times probably, and I don't know the conditions for it to work properly.

  • The Restart ntpd Beta Feature does nothing. After clicking it, I get this every single time:

Jun 28 11:12:25 iRobot- user.notice ntpd: Server 'ntpd' was stopped gracefully.
Jun 28 11:12:42 iRobot- user.notice ntpd: ntpd: timed out waiting for 162.159.200.123, reach 0x00, next query in 2s
Jun 28 11:12:42 iRobot- user.notice ntpd: ntpd: timed out waiting for 178.32.88.247, reach 0x00, next query in 2s
Jun 28 11:12:42 iRobot- user.notice ntpd: ntpd: timed out waiting for 178.215.228.24, reach 0x00, next query in 2s
Jun 28 11:12:42 iRobot- user.notice ntpd: ntpd: timed out waiting for 90.165.120.190, reach 0x00, next query in 2s
Jun 28 11:13:01 iRobot- user.notice ntpd: ntpd: timed out waiting for 2.59.235.35, reach 0x00, next query in 1s
Jun 28 11:13:01 iRobot- user.notice ntpd: ntpd: timed out waiting for 178.32.88.247, reach 0x00, next query in 2s
Jun 28 11:13:01 iRobot- user.notice ntpd: ntpd: timed out waiting for 89.140.186.3, reach 0x00, next query in 2s
Jun 28 11:13:01 iRobot- user.notice ntpd: ntpd: timed out waiting for 158.227.98.15, reach 0x00, next query in 1s

It does not work either, because it is configuring the Create3 as the server, but it seems the server never starts correctly.

Hopefully the user will have more "configuration power" and not have the create3 be a black box that prevents it from working unless it is in very simple setups.

PS I forgot to mention, I don't think it's a firewall issue either, I tried pinging those addresses that ntpd can't find from another machine in the same network and it arrives no problem.

@royito55
Copy link
Author

I found that for this case, the best "solution" is to factory reset the create3

@shamlian
Copy link
Collaborator

shamlian commented Jul 6, 2023

Not sure what to say here except that the log snippet you posted does indeed show the NTP daemon restarting.

You will find that we have just released G.5.1 / H.2.1 which allows direct configuration of ntp.conf; please feel free to reconfigure the daemon as you please, and let us know when you find a configuration which works in your particular use case.

@shamlian
Copy link
Collaborator

In case it helps: Clearpath has an example ntp.conf for the Turtlebot 4 use case; perhaps this can help with yours. turtlebot/turtlebot4#216

@shamlian
Copy link
Collaborator

Checking in again -- users have had some success with this -- see #401 . Would be curious to know if this solves your problem as well.

@shamlian
Copy link
Collaborator

Checking in one last time before I close this "cannot reproduce."

@shamlian shamlian closed this as completed Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants