NTP failed

Technical Support
1

How to resolve this problem regarding ntp.

2024 073 12:06:28: NTP failed to start, and we have an interent connection, trying to restart it…
Job for ntpdate.service failed because a timeout was exceeded.
See “systemctl status ntpdate.service” and “journalctl -xe” for details.

Mar 13 12:04:53 raspberryshake ntpd[464]: ntpd [email protected] (1): Starting
Mar 13 12:04:53 raspberryshake ntpd[464]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:111
Mar 13 12:04:53 raspberryshake systemd[1]: Started Network Time Service.
Mar 13 12:04:53 raspberryshake ntpd[482]: proto: precision = 0.778 usec (-20)
Mar 13 12:04:53 raspberryshake ntpd[482]: restrict 0.0.0.0: KOD does nothing without LIMITED.
Mar 13 12:04:53 raspberryshake ntpd[482]: restrict ::: KOD does nothing without LIMITED.
Mar 13 12:04:53 raspberryshake ntpd[482]: restrict: ignoring line 38, mask ‘::’ unusable.
Mar 13 12:04:53 raspberryshake ntpd[482]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING
Mar 13 12:04:53 raspberryshake systemd[1]: ntp.service: Main process exited, code=exited, status=1/FAILURE
Mar 13 12:04:53 raspberryshake systemd[1]: ntp.service: Failed with result ‘exit-code’.

1 Like
2

Hello rhoelmarcos15, and welcome to the community!

With only this portion of the logs, what you’re seeing could be related to unopened ports on your modem/router.

For the Shake to be able to find and connect to any NTP server, port 123 has to be open on your local network.

Could you please send the full logs when you can? So that I can check the entire Shake environment to see if there is anything else that could be causing the issue.

Thank you.

3

Hi Stormchaser,

see attached logs.

RSH.R9B74.2024-03-20T03_31_09.logs.tar (1.5 MB)

2 Likes
4

Thank you for the logs rhoelmarcos.

I can confirm that there is something blocking NTP data from being accessed by the Shake, as you have a good general internet connection and successful booting process.

I have tried to ping the three NTP servers and I got positive response on each, so they are good addresses:

Ping statistics for 222.127.1.21:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 271ms, Maximum = 280ms, Average = 274ms

Ping statistics for 222.127.1.25:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 261ms, Maximum = 278ms, Average = 270ms

Ping statistics for 222.127.1.19:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 272ms, Maximum = 306ms, Average = 284ms

Could you please check, via your modem/router administration panel, if port 123 is open or closed? If the second, please open it in UDP to allow time synchronization data to come in for the Shake.

If required, this is a general guide on how to do so: How to open ports on a router: Step-by-step guide | NordVPN. However, I recommend checking your router’s manual so that you are sure about the exact procedure.

If, instead, port 123 appears to be open, then there could be something not working with the Shake OS. In this case, I would then recommend re-burning the microSD card after formatting and erasing all its data/partitions first, and see how the Shake behaves with the newly installed system.

I will leave the burning instructions link here for your convenience: microSD card topics

If it doesn’t, wait for around 30 minutes after the last post-reburn Shake reboot, download the new logs and then send them to me.

Thank you for your collaboration.

5

Thanks Stormchaser.

I just edit ntp servers on /etc/ntp.conf

server 1.debian.pool.ntp.org iburst
server 2.debian.pool.ntp.org iburst
server 3.debian.pool.ntp.org iburst

to

server 1.asia.pool.ntp.org iburst
server 2.asia.pool.ntp.org iburst
server 3.asia.pool.ntp.org iburst

myshake@raspberryshake:/opt/log $ more postboot.log
2024 082 03:35:35: Cleaning up any dangling Docker data…
2024 082 03:35:36: Starting the FE Config Server
2024 082 03:35:39: adding fallback DNS servers to /etc/resolv.conf file
2024 082 04:27:44: We have an internet connection
2024 082 04:27:45: NTP failed to start, and we have an interent connection, trying to restart it…
2024 082 04:27:56: We have NTP services
2024 082 04:27:56: Checking for software updates, see upgrade.log for details
2024 082 04:28:05: Software Version : v0.20
2024 082 04:28:05: Setting Serial Port Name: HW Revision: b03115 / Port Name: /dev/ttyS0
2024 082 04:28:05: Discovered Instrument: RSHAKE.4D
2024 082 04:28:05: Ethernet is ON and WiFi interface is disabled. To enable, see file /opt/settings/user/enable-wifi.conf
2024 082 04:28:06: Retrieving IP Address of interface eth0: 192.168.10.165
2024 082 04:28:07: Retrieving MAC Address of interface eth0: e4:5f:01:c0:9b:59
2024 082 04:28:07: Defining Station Name: R9B59
2024 082 04:28:07: Generating SWARM.zip file
2024 082 04:28:07: Setting up cron jobs
2024 082 04:28:07: Configuring SEEDLINK…
2024 082 04:28:07: Generating necessary SC key files
2024 082 04:28:07: Configuring OWS
2024 082 04:28:07: Configuring HELI
2024 082 04:28:07: Starting R-SHAKE Data Containers…
2024 082 04:28:07: Starting Docker Container dataP
2024 082 04:28:09: Starting Docker Container dataC
2024 082 04:28:11: R-Shake System boot-up sequence completed

I think our ISP is blocking the other ntp server.

Thanks again…,

RHOEL

1 Like
6

Hello rhoelmarcos,

Yes, there definitely was something blocking access to the previous NTP server, probably your ISP as you have deduced.

Great to hear that the new one is not hampered and that you can now use your Shake without further issue!

You’re welcome.