One of my shakes produces data with gaps (serval per day, short gaps around 0.2s).
This shakes 3D outdoor is synchronized thourgh remote NTP (no GPS antenna).
I am collecting the data thourgh seedlink, but I merge those realtime datas with the one collected on the fdsnWS.
Could those gaps may due to NTP syncrhonization/resynchro ?
I would need the logs from the Shake to check what could be causing the gaps. If you can provide them I can give you a more detailed answer, thank you.
As usual, the instructions on how to get them are here: Please read before posting!
Thanks for your answer,
Here is the logs file.
Let me know.
RSH.R1992.2021-06-09T10_16_12.logs.tar (2.89 MB)
Thank you for the logs. Your intuition was correct in the end. As you can see from the excerpt below:
2021 155 17:50:07>> Connection succeeded to DDS server. 2021 155 17:52:24>> Time adjustment M0: HARD RESET. This will result in a one-time time-tear. 2021 155 17:52:24>> 5.0: NTP Time (Init): NTP: 1622829144.171849489 2021 155 17:52:24>> 5.2: NTP Sync (HARD): VEL Before: 1622829142.839999914 After: 1622829143.911000013 Diff: 1.071000099 2021 155 17:58:17>> Time adjustment M0: HARD RESET. This will result in a one-time time-tear. 2021 155 17:58:17>> 5.0: NTP Time (Init): NTP: 1622829497.038714886 2021 155 17:58:17>> 5.2: NTP Sync (HARD): VEL Before: 1622829497.921000004 After: 1622829496.778000116 Diff: -1.142999887 2021 155 18:10:26>> Connection succeeded to DDS server.
the Shake is regularly connecting to our servers to transmit data, but every now and then there are these hard resets that will result in a very short tear (as you saw, around 0.2 seconds) due to NTP resynchronization.
If you can, adding a GPS antenna should solve the issue, granting constant time synchro at any time.
Thanks for you answer. I will try to find a solution but on that site I can’t install GPS antenna…The NTP should work better, I am surpised.
Also do you know why I get this error (while this command is given in your docs) :
myshake@raspberryshake:/etc $ sudo systemctl restart ntp
Failed to restart ntp.service: Unit ntp.service not found.
Just to inform you, I have tested on another shake (R8A70) the command "sudo systemctl restart ntp” works….something wrong on the R1992 ? Missing packet that explains the ntp issue ?
Could you please execute the following command
for both Shakes, and post the results?
Here is the "ntpq -p” result for the shake R1992 :
remote refid st t when poll reach delay offset jitter
This response from that command was quite unexpected. Let’s try to start from scratch to understand what is going on.
Please shut off both Shakes, then your modem/router. Wait for around 5 minutes, then turn on your modem/router again. When internet is available again, only then turn on both Shakes again.
Wait for ~30 minutes, download both Shakes logs and please post them here.
Then, Please login into both Shakes, one at a time, execute the
ntpq -p command, and please post the two results in your message.
In this way I will have fresh logs and fresh NTP service response, to try and understand where the issue is by comparing the two units.
Those two shakes are remotely installed, unsightly 3G modems, and I can’t do what you ask.
I can remotely reboot the shakes, reboot the modem, but that’s all.
Should I proceed anyway ?
Yes, let’s try all the same with a restart for both Shakes. After having done it, wait for ~30 minutes, download both Shakes logs and please post them here.
Then, one Shake at a time, execute the ntpq -p command, and please post the two results in your message.
I have an issue to connect on the remote shakes.
I am not sure but I think someone (not me) has changed the “myshake” password…I could not authentifie by ssh or by the web page to reboot the shakes…
Do you have any backdoor (root login) to reset the “myshake” user password ?
Unfortunately not, for security purposes there is no backdoor. The only way to reset the password in such cases is to physically re-burn the microSD card from scratch.
Arghhh, no ssh root login ?
The ssh root login is the one with the default username and password that we provide.
It is why we recommend to secure the Shake as soon as the configuration has been completed, to avoid any possible intrusion or network violation via the Shake itself.
You will need to acquire the new password from the person who has changed it, otherwise, it is not possible to proceed forward.