RD3C0 not connected to the server

Technical Support
1

Hi,
I purchased the RS4D DIY kit from raspberryshake.org 4 days ago and received it today (June 22, 2023 Beijing time) and installed it on my own Raspberry PI 4B.
After starting up, my RS4D can normally read the data of all channels, but I cannot connect to the server when I turn on the data forwarding. And I also can’t in my RS4D equipment found on stationview.raspberryshake.org and shakenet.raspberryshake.org.
I tried the problem for a long time and there was still a problem.
Below is some station information, log files, and some important things I noticed.

Station code: RD3C0
Shake Model: RS4D
Raspberry Pi Model: Raspberry Pi 4B

Important things I noticed:

2023 173 10:58:34>> Srvr returned code (3), unable to connect.
2023 173 10:58:34>> Some meta-data is invalid, trying again.
2023 173 10:58:34>> Srvr returned code (3), unable to connect.
2023 173 10:58:34>> Some meta-data is invalid, trying again.
2023 173 10:58:36>> Srvr returned code (3), unable to connect.
2023 173 10:58:36>> Some meta-data is invalid, trying again.
2023 173 10:58:37>> Srvr returned code (3), unable to connect.
2023 173 10:58:37>> Some meta-data is invalid, trying again.
2023 173 10:58:37>> Unable to successfully connect after 10 tries, giving up.
2023 173 10:58:37>> Station will be locally black-listed until data services are restarted.
2023 173 10:58:37>> Station is black-listed, unable to connect, data will not be forwarded.

Log:
RSH.RD3C0.2023-06-22T14-09-34.logs.tar (740 KB)

2

Hello CatsYezuan, and welcome to the community!

Thank you for contacting us regarding this issue you are experiencing, and for sending the logs from your Shake.

From them, it appears that the start-up procedure is more than fine, and the Shake activates all that’s needed to work. The problems appear, as you have noticed, at the connection stage. These lines show it more clearly:

2023 173 10:50:55: R-Shake System boot-up sequence completed
2023 173 10:51:15: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2023 173 10:52:15: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available

2023 173 10:59:15>>	Time adjustment M0: HARD RESET.  This will result in a one-time time-tear.
2023 173 10:59:15>>	5.0: NTP Time (Init): NTP:	1687431555.634973526
2023 173 10:59:15>>	5.2: NTP Sync (HARD): VEL Before: 1687431554.898999929	After: 1687431555.374000072	Diff: 0.475000143
2023 173 10:59:15>>	5.2: NTP Sync (HARD): ACC Before: 1687431554.898999929	After: 1687431555.374000072	Diff: 0.475000143

This results in what you have seen in the other log file, which you have posted in your message. That is also why your Shake is not appearing, for now, on StationView and ShakeNet.

Could I please ask you to shut down both the Shake and your modem/router, start the modem/router again, wait for it to regain internet connection, turn on the Shake, and see if now the unit can connect?

Please also check that all cables are firmly inserted in their sockets, as sometimes this can be the cause of missing internet connectivity.

If you still don’t have connectivity, try plugging in the LAN Ethernet cable to another socket in the modem/router that you have, or also try to change the cable with another one that you have at home. You can easily test if everything works with another device, such as a laptop or home pc.

Finally, check the firewall settings of your modem/router to see if something software-side could be blocking the connection. You should be able to find everything in the administration panel of your modem/router.

If, after all these tests, the Shake still doesn’t connect, please wait for ~30 minutes, download the new logs and send them to me.

Thank you for your collaboration.

3

Hello Stormchaser,
Glad to receive your reply!
But my Raspberry shake 4D isn’t a network issue right now, the issue I’ve found multiple times in my logs is a metadata issue.
I have tried to reboot my router and rs4D device and my current inability to connect to the server still persists.

Here is the new log:
RSH.RD3C0.2023-06-23T11-00-24.logs.tar (1.1 MB)

1 Like
4

Hello CatsYezuan,

No problem at all! And thank you for the new logs. The range of tests you have performed allowed us to fully exclude the connectivity issue and we are now focusing on the investigation of the metadata one.

I will update you as soon as I have news.

5

Hello again CatsYezuan,

We have deployed a fix on our servers. Could I please ask you to reboot your Shake, when you have the chance, and check if now it manages to connect without issues?

If not, can you download the new logs and post them here?

Thank you.

6

Hello Stormchaser,

At around 6:00 on June 24, 2023, Beijing time, my raspberry shake 4D device could successfully connect to the server and transmit observation data after being restarted

Thank you so much for your help!

2 Likes
7

You’re more than welcome CatsYezuan, happy to help!

Enjoy your Shake!