I just installed a RS3D at our university using the ethernet port. I am able to access the seismometer (rs.local) and enabled data forwarding. I am getting the Server Connection: Not Connected error, and I guess this may be a firewall issue here but figured I’d ask first if there is a possible solution.
i do not see any attempt on the data server from your unit to make a connection. this indicates that the request is, in fact, not making it through to the server. most likely firewall issues on your uni network.
please verify ports 55555 and 55556 are open to the outside internet, as described in the manual page here.
Hello, I’m having similar issues connecting to the servers as dbeebe so I thought I’d post on here rather than starting a new topic, so hopefully this will get picked up!
I’m setting up a RS1D for the first time but it doesn’t seem to be connecting to the servers. I’ve attached my log file below. I’ll be interested to know if this is a unit issue or my internet (more likely) as I’ve had to bring home 13 shakes and a boom home from university as the network there was not welcoming to my shakes!
2020 221 09:24:04>> NTP timing is not available, so an accurate data timestamp is also not possible.|
2020 221 09:24:04>> Data will be streamed locally only using HOST Computer's clock time!|
2020 221 09:24:04>> If Data-Sharing is desired, NTP *must* be available before this can happen!|
which explains why you are not getting connected to the server.
from the logfile postboot.log:
2020 221 09:23:49: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2020 221 09:23:52: NTP failed to start, continuing without it
2020 221 09:23:52: There is still no internet connection after 132 seconds. Timing will not be accurate until NTP is available!
2020 221 09:23:52: System will check network status every 60 seconds. When network connection is detected, services will automatically restart.
which explains why there is no NTP services, since the NTP daemon needs NTP servers to get its time from, which requires a DNS server to resolve the server names.
from the logfile myshake.out:
Nameservers : 22.214.171.124
which looks a bit strange if you are on a home network. i will guess that this DNS server is not accessible from your home network, and so accessing NTP servers and Shake data servers will not be possible.
Thank you for explaining the situation! There are two possible ways - setting a manual IP and DNS in the http://rs.local web config, or adding a line to /etc/dhcpcd.conf in the Shake filesystem.
The first doesn’t require logging into the Shake. Navigate to rs.local, make note of the Shake’s IP address, then click on the Settings gear icon (high on the left) to access the configuration menu.
Click on NETWORK, then under ETHERNET SETTINGS, click on “Enable static IP”.
Fill out the Static IP field with the address you copied from the front page.
Fill out the DNS server field with the server of your choice or a generic but reliable DNS service. OpenDNS, which is 126.96.36.199, is a good choice. You can also use Cloudflare DNS service by entering 188.8.131.52 or Google by entering 184.108.40.206.
The second way, a bit more complex, in which you can keep your Shake on a dynamic IP (assigned by your modem/router):
Sorry for the slow reply, I sadly didn’t have time to play with the shake yesterday!
I initially tried the ssh method and I couldn’t get this to work. I actually wasn’t able to paste the commands into the terminal once I was connected to the shakes via ssh so I manually typed the commands (I think correctly!). Maybe as I wasn’t able to paste I was doing something wrong? When I ran that final command I didn’t get the same file output as you.
So I tried the static IP method instead. This isn’t working either. When I define the IP and DNS, I click save and reboot. Once the shake is done rebooting, I still have no network connection after 5-10 mins. When I go back to the Network settings page, the tick box is unticked, the IP is undefined and the DNS is 220.127.116.11 even when I’ve set other DNS servers. I tried both method a few times!
I understand the new issue with the static IP method. We have seen that sometimes pops up, but it is very random, so we haven’t been able to pinpoint the exact cause.
Could you please post a screenshot of the current content of the resolv.conf file that you tried to edit?
And, can you try to edit it again via SSH? The usual Ctrl+C and Ctrl+V combination does not work in the command line window, and you need to right-click on the window itself and then select paste from the menu to actually paste the commands I listed.
See if in this way you are able to manually edit that file, if you haven’t already tried such a method.
Okay - that copy and paste info was very helpful! The commands seem to have worked this time although the output is slightly different from what you suggested but I think it looks positive. Sadly though my shake has not connected to the server still. I’ve left it for 15/20 mins to see. I will keep checking in on it throughout the day just in case.
Hi Stormchaser I’d like to just add another data log from a second RS1D I have just set up which has connected to the servers straight away. I wonder if this will be able to help you pinpoint the issue with the first one. Thanks!
thank you for the new logs. It’s easy to see that this one is working perfectly as it should, and the fact that is connected to the same network as the other make the errors we were seeing a bit baffling.
Could you please post the screenshots of the dhcpcd.conf and resolv.conf files of this second working Shake? Thank you.
Okay here are the screenshots from the working shake which to be clear I haven’t set a static IP on. The resolv.conf worked fine but the dhcpcd.conf looks like there was nothing in it? Is there a way to factory reset the non working shake? I just wonder if something got jumbled when I was trying to connect it to my university network?
Additional info is I’ve set up a further 4 shakes (RS4Ds this time) and they were fine too.
perfect, that’s what I wanted to see (and thank you for the confirmation that the other Shakes are working nominally).
As you have surely understood, this is what normal files look like, and there is an evident issue with the configuration of the first Shake. We can try a last thing before resetting everything:
please open the dhcpcd.conf file with
sudo nano /etc/dhcpcd.conf
and delete all the lines that start with static, thus leaving only interface eth0. Do not modify anything else.
sudo service dhcpcd restart
to make sure those changes took hold and then check the output file with
The file should look like the one from your working Shake.
If it doesn’t, then a reset is the best option left on the table. I can advise to:
re-burn the ShakeOS on your current microSD card
or get a new microSD (to erase the chance that this one got ruined) and burn the Shake OS there.
I know that this means to retrieve the Shake from its remote location, or going there personally, but there is no other way of correcting this via remote actions.
In both mentioned cases, these are the instructions to prepare the new OS image:
Please take the microSD card you have and format it before burning the new Shake OS image
Make sure, when you format it, that the shown capacity is the maximum (i.e. if the SD card is 32GB like yours, then the capacity should be near or equal to that value). This is to check that no partitions have been involuntarily and erroneously created. They could be the cause of the error we see now
Take care to format the SD card in a FAT32 File System (or exFAT if the SD card is 64GB or larger)