Unable to see in Shakenet - AM.R83B4.00.EHZ

RSH.R83B4.2022-10-25T23_58_11.logs.tar (3.0 MB)

I have moved to a new location and unable to bring back the device online on the shakenet. i can see the device on the rs.local and it shows connected to internet.

hake Model : RS1D
Raspberry Pi Model : 3 Model B
System Status : RUNNING
System Version : 0.20
WiFi Local IPv4 : 10.0.0.191
WiFi MAC : b8:27:eb:99:d6:e1
Data Producer : ON
Data Consumer : ON
Off-line Mode : OFF
Data Forwarding : ON
Server Connection : Connected

Thanks for your help :slight_smile:

Hello gt6067, welcome to our community.

Thank you for the logs from your Shake. Nothing particular “pops out” but clearly there is something that is not working properly as the station is not yet appearing on our services.

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, wait for ~30 minutes from this point, download the logs and send them to me again?

I want to check if, after a fresh start, there are some changes compared to what I have available now.

Thank you for your cooperation.

Hi my station is AM.R71EF
I do not appear on shakenet yet, it is my first time using my RS3D, all is conected and is shows correctly as you can see here:


I can see helicorder data and use swarm, I had to change rp date and time manually.RSH.R71EF.2022-10-29T01_09_41.logs.tar (1.3 MB)

After a quick look at the logs, there seems to be a problem with time sync (NTP) - which you noticed and set the time manually. I think that is your problem. What we see is:

Oct 27 23:03:04 raspberryshake ntpd[16474]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Oct 27 23:03:04 raspberryshake ntpd[16474]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

     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
 ntp71.kashra-se .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 ntp33.kashra-se .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 45.87.78.35     .INIT.          16 u    - 1024    0    0.000    0.000   0.000

The system was able to resolve the names of the NTP servers ok - so DNS is working.
But the NTP connections are all stuck in the INIT phase.
The most likely cause is that you have a firewall blocking the NTP port (123) between the R-Shake and the Internet.

Hello Jmguerra,

Yes, as Philip said, there seems to be an issue with your time sinchronization service (NTP), which regulates the data transmission to our servers. 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, wait for ~30 minutes from this point, download the logs and send them to me again?

Furthermore, we are currently experiencing internal issues that are causing recently connected stations to not be visible on our services (StationView, DataView, etc.) and are working to solve them as quickly as possible. Hopefully, everything will be solved by the end of today (US time), but I will update you again as soon as I have news from our server team.

Thank you very much for your understanding and patience in this.