NTP and rs.local not working

FlyingMoose · January 5, 2025, 3:33am

I just got a Raspberry Shake 4D (pre-assembled indoor version). I live outside the US, but I ordered it while in the US and tested it. It worked fine on my mom’s internet connection.

Now I am back in the Philippines and I am having lots of trouble getting it to connect to the server, trouble accessing rs.local, and NTP keeps failing. [Update: Actually I believe it is able to connect to the server either way, I just hadn’t waited long enough.]

If I plug it into my Deco Mesh network, I can access rs.local but NTP doesn’t work. (ethernet cable to Deco, so it’s only acting as a router for the RS, not WiFi).

If I plug it into the ISP modem directly, I can’t access rs.local so I can’t tell if it’s working. (I don’t have a HDMI monitor except my 65" TV so it’s not too practical to attach KVM).

Note that for both networks above, I made sure my laptop was on the same network as the RS when trying to access rs.local.

Here is the log while on Deco (postboot.log) (NTP doesn’t work but rs.local works):

2024 342 13:17:19: Cleaning up any dangling Docker data...
2024 342 13:17:20: Starting the FE Config Server
2024 342 13:17:25: adding fallback DNS servers to /etc/resolv.conf file
2024 342 13:17:27: We have an internet connection
2024 342 13:17:27: 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.
2024 342 13:19:01: 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.
2024 342 13:20:35: 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.
2024 342 13:22:09: 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.
2024 342 13:23:44: 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.
2024 342 13:25:18: 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.
2024 342 13:26:52: 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.
2024 342 13:28:26: 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.
2024 342 13:30:00: 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.
2024 342 13:31:34: 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.
2024 342 13:33:07: NTP failed to start, continuing without it
2024 342 13:33:07: Checking for software updates, see upgrade.log for details
2024 342 13:33:16: Software Version : v0.20
2024 342 13:33:17: Setting Serial Port Name: HW Revision: a020d3 / Port Name: /dev/ttyS0
2024 342 13:33:17: Discovered Instrument: RSHAKE.4D
2024 342 13:33:17: Ethernet is ON and WiFi interface is disabled. To enable, see file /opt/settings/user/enable-wifi.conf
2024 342 13:33:18: Retrieving IP Address of interface eth0: 192.168.68.54
2024 342 13:33:18: Retrieving MAC Address of interface eth0: b8:27:eb:1a:6d:50
2024 342 13:33:19: Defining Station Name: R6D50
2024 342 13:33:19: Generating SWARM.zip file
2024 342 13:33:25: Setting up cron jobs
2024 342 13:33:25: Configuring SEEDLINK...
2024 342 13:33:25: Generating necessary SC key files
2024 342 13:33:25: Configuring OWS
2024 342 13:33:25: Configuring HELI
2024 342 13:33:26: Starting R-SHAKE Data Containers...
2024 342 13:33:26: Starting Docker Container dataP 
2024 342 13:33:31: Starting Docker Container dataC
2024 342 13:33:32: R-Shake System boot-up sequence completed
 
2024 342 13:34:01: Network connection detected, system is restarting...
2024 342 13:34:01: Stopping R-Shake Data Services
2024 342 13:34:04: Restarting Networking and NTP Services
Job for ntpdate.service failed because a timeout was exceeded.
See "systemctl status ntpdate.service" and "journalctl -xe" for details.
2024 342 13:35:35: Starting R-Shake Data Services
2024 342 13:35:35: Ethernet is ON and WiFi interface is disabled. To enable, see file /opt/settings/user/enable-wifi.conf
2024 342 13:35:35: Retrieving IP Address of interface eth0: 192.168.68.54
2024 342 13:35:36: Generating necessary SC key files
2024 342 13:35:36: Configuring SEEDLINK...
2024 342 13:35:36: Configuring OWS
2024 342 13:35:36: Configuring HELI
2024 342 13:35:36: Starting R-SHAKE Data Containers...
2024 342 13:35:36: Starting Docker Container dataP 
2024 342 13:35:38: Starting Docker Container dataC
2024 342 13:35:40: System restarted

And here is the log from when it’s attached to the internet modem directly (From previous boot, postboot.log.old):

2023 139 16:03:25: Cleaning up any dangling Docker data...
2023 139 16:03:25: Starting the FE Config Server
2024 340 21:10:33: adding fallback DNS servers to /etc/resolv.conf file
2024 340 21:10:36: We have an internet connection
2024 340 21:10:36: NTP failed to start, and we have an interent connection, trying to restart it...
2024 340 21:10:47: We have NTP services
2024 340 21:10:47: Checking for software updates, see upgrade.log for details
2024 340 21:10:51: Software Version : v0.20
2024 340 21:10:51: Setting Serial Port Name: HW Revision: a020d3 / Port Name: /dev/ttyS0
2024 340 21:10:51: Discovered Instrument: RSHAKE.4D
2024 340 21:10:52: Ethernet is ON and WiFi interface is disabled. To enable, see file /opt/settings/user/enable-wifi.conf
2024 340 21:10:53: Retrieving IP Address of interface eth0: 10.0.1.15
2024 340 21:10:53: Retrieving MAC Address of interface eth0: b8:27:eb:1a:6d:50
2024 340 21:10:53: Defining Station Name: R6D50
2024 340 21:10:53: Generating SWARM.zip file
2024 340 21:11:04: Setting up cron jobs
2024 340 21:11:04: Configuring SEEDLINK...
2024 340 21:11:04: Generating necessary SC key files
2024 340 21:11:04: Configuring OWS
2024 340 21:11:04: Configuring HELI
2024 340 21:11:04: Starting R-SHAKE Data Containers...
2024 340 21:11:04: Starting Docker Container dataP 
2024 340 21:11:07: Starting Docker Container dataC
2024 340 21:11:09: R-Shake System boot-up sequence completed
 
 
2024 342 00:17:20: Cleaning up any dangling Docker data...
2024 342 00:17:22: Starting the FE Config Server
2024 342 00:17:31: adding fallback DNS servers to /etc/resolv.conf file
2024 342 00:17:33: We have an internet connection
2024 342 00:17:34: 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.
2024 342 00:19:07: 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.
2024 342 00:20:41: 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.
2024 342 00:22:15: 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.
2024 342 00:23:49: 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.
2024 342 00:25:23: 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.
2024 342 00:26:57: 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.
2024 342 00:28:31: 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.
2024 342 00:30:05: 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.
2024 342 00:31:39: 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.
2024 342 00:33:12: NTP failed to start, continuing without it
2024 342 00:33:12: Checking for software updates, see upgrade.log for details
2024 342 00:33:22: Software Version : v0.20
2024 342 00:33:22: Setting Serial Port Name: HW Revision: a020d3 / Port Name: /dev/ttyS0
2024 342 00:33:22: Discovered Instrument: RSHAKE.4D
2024 342 00:33:22: Ethernet is ON and WiFi interface is disabled. To enable, see file /opt/settings/user/enable-wifi.conf
2024 342 00:33:23: Retrieving IP Address of interface eth0: 192.168.254.105
2024 342 00:33:24: Retrieving MAC Address of interface eth0: b8:27:eb:1a:6d:50
2024 342 00:33:24: Defining Station Name: R6D50
2024 342 00:33:24: Generating SWARM.zip file
2024 342 00:33:30: Setting up cron jobs
2024 342 00:33:30: Configuring SEEDLINK...
2024 342 00:33:30: Generating necessary SC key files
2024 342 00:33:30: Configuring OWS
2024 342 00:33:30: Configuring HELI
2024 342 00:33:30: Starting R-SHAKE Data Containers...
2024 342 00:33:30: Starting Docker Container dataP 
2024 342 00:33:34: Starting Docker Container dataC
2024 342 00:33:35: R-Shake System boot-up sequence completed
 
2024 342 00:34:02: Network connection detected, system is restarting...
2024 342 00:34:02: Stopping R-Shake Data Services
2024 342 00:34:04: Restarting Networking and NTP Services
Job for ntpdate.service failed because a timeout was exceeded.
See "systemctl status ntpdate.service" and "journalctl -xe" for details.
2024 342 00:35:35: Starting R-Shake Data Services
2024 342 00:35:35: Ethernet is ON and WiFi interface is disabled. To enable, see file /opt/settings/user/enable-wifi.conf
2024 342 00:35:35: Retrieving IP Address of interface eth0: 192.168.254.105
2024 342 00:35:36: Generating necessary SC key files
2024 342 00:35:36: Configuring SEEDLINK...
2024 342 00:35:36: Configuring OWS
2024 342 00:35:36: Configuring HELI
2024 342 00:35:36: Starting R-SHAKE Data Containers...
2024 342 00:35:36: Starting Docker Container dataP 
2024 342 00:35:38: Starting Docker Container dataC
2024 342 00:35:40: System restarted
 
2024 342 00:17:23: Cleaning up any dangling Docker data...
2024 342 00:17:24: Starting the FE Config Server
2024 342 00:17:32: adding fallback DNS servers to /etc/resolv.conf file
2024 342 00:17:47: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2024 342 00:17:47: No internet connection found
2024 342 00:17:47: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2024 342 00:17:50: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2024 342 00:17:53: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2024 342 00:17:56: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2024 342 00:17:59: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2024 342 00:18:03: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2024 342 00:18:06: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2024 342 00:18:09: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2024 342 00:18:12: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2024 342 00:18:15: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2024 342 00:18:18: NTP failed to start, continuing without it
2024 342 00:18:18: There is still no internet connection after 31 seconds. Timing will not be accurate until NTP is available!
2024 342 00:18:18: System will check network status every 60 seconds.  When network connection is detected, services will automatically restart.
2024 342 00:18:18: Note: if you have a WiFi adapter enabled, confirm that the WMM Wireless Configuration setting on the router is enabled!
2024 342 00:18:18: Software Version : v0.20
2024 342 00:18:19: Setting Serial Port Name: HW Revision: a020d3 / Port Name: /dev/ttyS0
2024 342 00:18:19: Discovered Instrument: RSHAKE.4D
2024 342 00:18:19: Ethernet is ON and WiFi interface is disabled. To enable, see file /opt/settings/user/enable-wifi.conf
2024 342 00:18:20: Retrieving IP Address of interface eth0: 192.168.254.102
2024 342 00:18:20: Retrieving MAC Address of interface eth0: b8:27:eb:1a:6d:50
2024 342 00:18:21: Defining Station Name: R6D50
2024 342 00:18:21: Generating SWARM.zip file
2024 342 00:18:27: Setting up cron jobs
2024 342 00:18:27: Configuring SEEDLINK...
2024 342 00:18:27: Generating necessary SC key files
2024 342 00:18:27: Configuring OWS
2024 342 00:18:27: Configuring HELI
2024 342 00:18:27: Starting R-SHAKE Data Containers...
2024 342 00:18:27: Starting Docker Container dataP 
2024 342 00:18:36: Starting Docker Container dataC
2024 342 00:18:37: R-Shake System boot-up sequence completed
 
2024 342 00:19:03: Network connection detected, system is restarting...
2024 342 00:19:03: Stopping R-Shake Data Services
2024 342 00:19:05: Restarting Networking and NTP Services
Job for ntpdate.service failed because a timeout was exceeded.
See "systemctl status ntpdate.service" and "journalctl -xe" for details.
2024 342 00:20:37: Starting R-Shake Data Services
2024 342 00:20:37: Ethernet is ON and WiFi interface is disabled. To enable, see file /opt/settings/user/enable-wifi.conf
2024 342 00:20:37: Retrieving IP Address of interface eth0: 192.168.254.102
2024 342 00:20:38: Generating necessary SC key files
2024 342 00:20:38: Configuring SEEDLINK...
2024 342 00:20:38: Configuring OWS
2024 342 00:20:38: Configuring HELI
2024 342 00:20:38: Starting R-SHAKE Data Containers...
2024 342 00:20:38: Starting Docker Container dataP 
2024 342 00:20:40: Starting Docker Container dataC
2024 342 00:20:42: System restarted
 
2024 342 12:09:27: Cleaning up any dangling Docker data...
2024 342 12:09:28: Starting the FE Config Server
2024 342 12:09:33: adding fallback DNS servers to /etc/resolv.conf file
2024 342 12:09:34: We have an internet connection
2024 342 12:09:35: 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.
2024 342 12:11:08: 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.
2024 342 12:12:42: 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.
2024 342 12:14:16: 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.
2024 342 12:15:50: 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.
2024 342 12:17:24: 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.
2024 342 12:18:59: 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.
2024 342 12:20:32: 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.
2024 342 12:22:07: 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.
2024 342 12:23:40: 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.
2024 342 12:25:14: NTP failed to start, continuing without it
2024 342 12:25:14: Checking for software updates, see upgrade.log for details
2024 342 12:25:24: Software Version : v0.20
2024 342 12:25:25: Setting Serial Port Name: HW Revision: a020d3 / Port Name: /dev/ttyS0
2024 342 12:25:25: Discovered Instrument: RSHAKE.4D
2024 342 12:25:25: Ethernet is ON and WiFi interface is disabled. To enable, see file /opt/settings/user/enable-wifi.conf
2024 342 12:25:26: Retrieving IP Address of interface eth0: 192.168.68.54
2024 342 12:25:26: Retrieving MAC Address of interface eth0: b8:27:eb:1a:6d:50
2024 342 12:25:26: Defining Station Name: R6D50
2024 342 12:25:26: Generating SWARM.zip file
2024 342 12:25:26: Setting up cron jobs
2024 342 12:25:27: Configuring SEEDLINK...
2024 342 12:25:27: Generating necessary SC key files
2024 342 12:25:27: Configuring OWS
2024 342 12:25:27: Configuring HELI
2024 342 12:25:27: Starting R-SHAKE Data Containers...
2024 342 12:25:27: Starting Docker Container dataP 
2024 342 12:25:30: Starting Docker Container dataC
2024 342 12:25:31: R-Shake System boot-up sequence completed
 
2024 342 12:26:01: Network connection detected, system is restarting...
2024 342 12:26:01: Stopping R-Shake Data Services
2024 342 12:26:04: Restarting Networking and NTP Services
Job for ntpdate.service failed because a timeout was exceeded.
See "systemctl status ntpdate.service" and "journalctl -xe" for details.
2024 342 12:27:36: Starting R-Shake Data Services
2024 342 12:27:36: Ethernet is ON and WiFi interface is disabled. To enable, see file /opt/settings/user/enable-wifi.conf
2024 342 12:27:36: Retrieving IP Address of interface eth0: 192.168.68.54
2024 342 12:27:36: Generating necessary SC key files
2024 342 12:27:36: Configuring SEEDLINK...
2024 342 12:27:36: Configuring OWS
2024 342 12:27:36: Configuring HELI
2024 342 12:27:37: Starting R-SHAKE Data Containers...
2024 342 12:27:37: Starting Docker Container dataP 
2024 342 12:27:39: Starting Docker Container dataC
2024 342 12:27:41: System restarted
 
2024 342 12:18:41: Cleaning up any dangling Docker data...
2024 342 12:18:42: Starting the FE Config Server
2024 342 12:18:46: adding fallback DNS servers to /etc/resolv.conf file
2024 342 12:18:47: We have an internet connection
2024 342 12:18:48: 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.
2024 342 12:20:22: 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.
2024 342 12:21:56: NTP failed to start, and we have an interent connection, trying to restart it...

Stormchaser · January 5, 2025, 9:09pm

Hello FlyingMoose, and welcome to our community!

If rs.local/ is not working (which can happen with some local network infrastructures, mine included), you can access the same Shake management page using the instrument’s local IP address. This may make it easier to look at what’s happening.

Thank you for the two log snippets. Could I ask you to either 1) download the entire set by using the management page or 2) zip all content of the /opt/log folder on the Shake, and attach the zip file to your reply?

The complete log set will provide a better overview of your local situation.

Thank you.

FlyingMoose · January 5, 2025, 11:40pm

Thank you for your help.

I found the IP address of the RS (192.168.254.109 on LAN2 Port) and made sure I’m connected to the same network, but I still can’t get to it by going directly to that IP address. It just times out. I tried 3 different browsers (although it loads fine in my regular browser when it’s double-NATted through the Deco). I even tried all assigned IP addresses but none of them worked. I looked through all the modem settings but I couldn’t find anything that sounded like it would block the connection between WiFi and LAN. I suppose I could buy an ethernet dongle for my laptop and see if I can connect when plugged into the LAN instead of WiFi.

Here is the log file as requested. Note that it was made while double NATted, since I can’t connect to the RS otherwise, but hopefully you can see the information from the previous boot (when it was plugged into the modem directly).

RSH.R6D50.2024-12-08T09_10_47.logs.tar (739 KB)

FlyingMoose · January 6, 2025, 9:45am

I’ve been working on this more.

I figured out that going to the RS by IP or rs.local works if my computer is plugged into the same ethernet port as the RS (using an ethernet switch). If I plug it into a different port or connect to WiFi, I’m no longer able to connect. I’m guessing my ISP has port isolation.

But however it is connected, it’s still not able to use NTP to set the time.

If I can get it to set the time, I’ll try hooking it up to my Deco router again, but I figure it’ll be easier to solve the NTP problem if it’s not behind a double NAT.

I looked at the port forwarding in my modem, and I’m not sure what all the settings need to be (specifically the public IP address of the NTP server). Here is the screen:

Now that I’m able to connect to it, here’s the log from the current boot:

RSH.R6D50.2024-12-08T17_49_33.logs.tar (895 KB)

I don’t consider the current connection a solution because I don’t want ethernet cables draped all over the place and I want to use my laptop on WiFi (plus NTP not working).

I’ll note that my laptop has no problem setting the time automatically over the same connection.

Update: I plugged the Deco into the same switch (so all my LAN devices are on the same port) and if I connect to the Deco’s WiFi I can access the RS by IP (but not using rs.local). So while it’s not ideal, I’ll be doing ok if I can get NTP working.

Stormchaser · January 6, 2025, 12:35pm

Hello again,

Thank you for the two log sets and the further feedback about your troubleshooting.

As you were able to download the log files themselves, the fact that rs.local/ remains not accessible with one of the network configurations you tried seems to depend on the (local) network itself, and not on a Shake malfunction issue. The ISP port isolation clue might be the correct one.

Regarding NTP, I would suggest manually editing (using nano, vi, or your preferred editor) the /etc/NTP.conf file and adding time servers that are closer to your location, as explained here: NTP and GPS timing details.

For the Philippines, these are the recommended ones: pool.ntp.org: NTP Servers in Philippines, ph.pool.ntp.org. More generally, this is a comprehensive list for Asia: pool.ntp.org: NTP Servers in Asia, asia.pool.ntp.org.

Once done, you can reboot your Shake to see if these changes manage to get you connected to an NTP server, or you can execute the series of three commands in the manual page link above to achieve the same.

FlyingMoose · January 6, 2025, 2:39pm

Ok, I did the changes you recommended and NTP still couldn’t set the time.

I put in a port-forwarding rule for the first server and tried again, and the time finally got set correctly.

I tried adding rules for the other two servers, but I get this error:

Screenshot 2025-01-06 at 10.23.02 PM

I don’t fully understand port forwarding. I guess it’s not possible to let multiple external IP addresses be forwarded to an internal one, so I’m limited to one time server (which will stop working if the IP ever changes). Here’s the rule I have so far:

Even though the time is set, it doesn’t appear to be working:

myshake@raspberryshake:/etc $ timedatectl
               Local time: Mon 2025-01-06 14:31:43 UTC
           Universal time: Mon 2025-01-06 14:31:43 UTC
                 RTC time: n/a
                Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: no

Any suggestions would be appreciated.

FlyingMoose · January 6, 2025, 3:19pm

Another update: I tried all kinds of wildcards for the public IP address for NPT, none of which it accepted as valid, but it turns out I just had to leave it blank. I have no experience with port forwarding hehe.

Once I’m done with this, how can I check if NTP is working? timedatectl still says it’s not active:

myshake@raspberryshake:/opt $ timedatectl
               Local time: Mon 2025-01-06 15:19:09 UTC
           Universal time: Mon 2025-01-06 15:19:09 UTC
                 RTC time: n/a
                Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: no

Stormchaser · January 6, 2025, 4:58pm

Hello, thanks for the further updates.

Could you provide the:

Contents of /etc/ntp.conf
Output of command ‘ntpq -p’
Output of command ‘sudo journalctl -xn’ if and when ‘restart ntpd’ fails

Thank you.

FlyingMoose · January 6, 2025, 5:33pm

Thanks, here’s the info you requested.

/etc/ntp.conf:

tinker panic 0
# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help

driftfile /var/lib/ntp/ntp.drift


# Enable this if you want statistics to be logged.
#statsdir /var/log/ntpstats/

statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable


# You do need to talk to an NTP server or two (or three).
#server ntp.your-provider.example

# pool.ntp.org maps to about 1000 low-stratum NTP servers.  Your server will
# pick a different set every time it starts up.  Please consider joining the
# pool: <http://www.pool.ntp.org/join.html>

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

server 1.ph.pool.ntp.org
server 3.asia.pool.ntp.org
server 0.asia.pool.ntp.org

# Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for
# details.  The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions>
# might also be helpful.
#
# Note that "restrict" applies to both servers and clients, so a configuration
# that might be intended to block requests from certain clients could also end
# up blocking replies from your own upstream servers.

# By default, exchange time with everybody, but don't allow configuration.
restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery

# Local users may interrogate the ntp server more closely.
restrict 127.0.0.1
restrict ::1

# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
#restrict 192.168.123.0 mask 255.255.255.0 notrust


# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
#broadcast 192.168.123.255

# If you want to listen to time broadcasts on your local subnet, de-comment the
# next lines.  Please do this only if you trust everybody on the network!
#disable auth
#broadcastclient

    # GPS Serial data reference                          
    server 127.127.28.0 minpoll 4 maxpoll 4 noselect     
    fudge 127.127.28.0 time1 0.500 refid GPS             
    #                                                    
    # GPS PPS reference                                  
    server 127.127.28.1 minpoll 4 maxpoll 4 prefer       
    fudge 127.127.28.1 refid PPS

Output of ntpq -p:

myshake@raspberryshake:/etc $ ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 SHM(0)          .GPS.            0 l    -   16    0    0.000    0.000   0.000
 SHM(1)          .PPS.            0 l    -   16    0    0.000    0.000   0.000
 222.127.1.27    .STEP.          16 u    - 1024    0    0.000    0.000   0.000
*194.225.150.25  193.67.79.202    2 u  135  256  377  346.950  -11.712   0.294
+144.24.146.96   132.163.97.4     2 u  121  256  377  230.242   10.363   1.397

I haven’t had “restart ntpd” fail (at least, it never gave an error message, I didn’t check exit status). Here’s the output anyway:

**myshake@raspberryshake**:**/etc $** sudo journalctl -xn

-- Logs begin at Mon 2025-01-06 15:49:41 UTC, end at Mon 2025-01-06 17:31:29 UTC. --

Jan 06 17:00:03 raspberryshake sudo[23861]: pam_unix(sudo:session): session closed for user root

Jan 06 17:00:03 raspberryshake CRON[23557]: pam_unix(cron:session): session closed for user myshake

Jan 06 17:17:01 raspberryshake CRON[24913]: pam_unix(cron:session): session opened for user root by (uid=0)

Jan 06 17:17:01 raspberryshake CRON[24917]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Jan 06 17:17:01 raspberryshake CRON[24913]: pam_unix(cron:session): session closed for user root

Jan 06 17:30:19 raspberryshake sudo[25766]: **myshake : TTY=pts/0 ; PWD=/etc ; USER=root ; COMMAND=/bin/journalctl -xn**

Jan 06 17:30:19 raspberryshake sudo[25766]: pam_unix(sudo:session): session opened for user root by myshake(uid=0)

Jan 06 17:31:23 raspberryshake sudo[25766]: pam_unix(sudo:session): session closed for user root

Jan 06 17:31:29 raspberryshake sudo[25840]: **myshake : TTY=pts/0 ; PWD=/etc ; USER=root ; COMMAND=/bin/journalctl -xn**

Jan 06 17:31:29 raspberryshake sudo[25840]: pam_unix(sudo:session): session opened for user root by myshake(uid=0)

It seems like it’s working now. Maybe it just took some time to get going. These things (like messing with NTP and port forwarding) are things I know the concepts of but have never used before, so it’s taken me a bit of time to figure this all out. I’ve certainly learned a lot. Thanks for your help.

Update: I just noticed “iburst” at the end of the server lines, which I have now added to etc/ntp.conf:

server 1.ph.pool.ntp.org iburst
server 3.asia.pool.ntp.org iburst
server 0.asia.pool.ntp.org iburst

Updated output:

myshake@raspberryshake:/etc $ ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 SHM(0)          .GPS.            0 l    -   16    0    0.000    0.000   0.000
 SHM(1)          .PPS.            0 l    -   16    0    0.000    0.000   0.000
 222.127.1.19 (m .INIT.          16 u    -   64    0    0.000    0.000   0.000
+ntp.gnc.am      156.133.237.214  2 u   50   64    3  373.443  -48.122  26.654
*ntp.uii.net.id  .GPS.            1 u   50   64    3   70.693    6.371  24.746

Stormchaser · January 6, 2025, 8:36pm

Yes, everything seems to be working now, and I can see your live data flowing in: https://stationview.raspberryshake.org/#/?lat=10.32432&lon=123.90118&zoom=7.000&sta=R6D50.

The Shake is correctly getting NTP information from the server with the * before its line (the last), with an alternative valid candidate in the line above (marked with a +).

You’re right; sometimes, the learning curve can be pretty sharp, but I’m happy I could help.

FlyingMoose · January 7, 2025, 4:38am

Very good. So far, as I would assume happens with most new RS owners, I’ve been jumping up and down to watch it register on the graph… I live in a building of 500 condo units, in the middle of a busy city, so there’s lots of human noise to try to figure out.