My Raspberry Shake seems fine locally. I updated the network settings and the long/lat. However, the net shows it offline at its old location. Here is what it looks like locally. I’ve Googled and can’t figure this out on my own. I have a vague memory that one must get manual intervention from people in support. I see that “server connection” is not connected. But don’t know how to remedy that as it is connected to my LAN and my LAN has excellent connection to the Internet.
Data Producer|:|ON|
|Data Consumer|:|ON|
|Stand-Alone|:|OFF|
|Data Forwarding|:|ON|
|Server Connection|:|Not Connecte|
Here is some log bits that might help:
at Jan 9 19:21:29 2021 - seedlink: [odf] data is available
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59442 : opening connection
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59442 : .dummy : HELLO
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59442 : INFO STREAMS
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59442 : closing connection
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59446 : opening connection
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59446 : .dummy : HELLO
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59446 : INFO ID
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59446 : closing connection
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59450 : opening connection
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59450 : .dummy : HELLO
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59450 : INFO STREAMS
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59450 : closing connection
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59454 : opening connection
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59454 : .dummy : HELLO
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59454 : STATION R2370 AM
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59454 : R2370 : SELECT D
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59454 : R2370 : DATA
Sat Jan 9 19:21:54 2021 - seedlink: 172.17.0.2:59454 : END
Sat Jan 9 19:21:57 2021 - seedlink: 127.0.0.1:43902 : opening connection
Sat Jan 9 19:21:57 2021 - seedlink: 127.0.0.1:43902 : .dummy : HELLO
Sat Jan 9 19:21:57 2021 - seedlink: 127.0.0.1:43902 : STATION R2370 AM
Sat Jan 9 19:21:57 2021 - seedlink: 127.0.0.1:43902 : R2370 : DATA
Sat Jan 9 19:21:57 2021 - seedlink: 127.0.0.1:43902 : END
Hello Robert,
I see your issue, but I need more information to start troubleshooting the issue. Could you please post the logs from the Shake, so I can try to get more insight on what’s happening?
In case you don’t know or don’t remember how to do it, they are downloadable from the Raspberry Shake’s web configuration page, accessible entering the rs.local (or the Shake IP) address in your browser, then by clicking on the “Download Logs” button.
Thank you.
RSH.R2370.2021-01-10T11_47_52.logs.tar (2.8 MB)
Thanks for the quick response. Here are the logs, attached.
Rob
Hello Rob,
thank you for the logs, they confirmed what I was suspecting. Your issue can be found in the postboot.log file, where these lines explain that we are facing a DNS problem:
2021 009 19:18:56: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2021 009 19:18:56: No internet connection found
2021 009 19:19:06: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
The first thing you can try, if you haven’t already, is simply to shut down your modem/router, wait a couple of minutes, and then turn it on again, to see if it was a simple issue with the modem/router itself.
If the connection still doesn’t work, then you can also try to change the DNS on the Shake, as explained in this page on our manual, Firewall issues? — Instructions on Setting Up Your Raspberry Shake, to see if this solves the issue. I’ll add some more info below.
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 a more reliable DNS service. OpenDNS, which is 208.67.222.222, is a good choice. You can also use Cloudflare DNS service by entering 1.1.1.1 or Google by entering 8.8.8.8.
The second way, a bit more complex, in which you can keep your Shake on a dynamic IP (assigned by your modem/router):
-
SSH into the Shake (guide here: How to access your Raspberry Shake’s computer via ssh — Instructions on Setting Up Your Raspberry Shake)
Once you’re in, copy and paste these commands (this example is for Cloudflare DNS):
sudo echo 'static domain_name_servers=1.1.1.1 1.0.0.1' >> /etc/dhcpcd.conf
sudo service dhcpcd restart
Now make sure those changes took hold:
nano /etc/resolv.conf
The file should look like the following:
# Generated by resolvconf
nameserver 1.1.1.1
nameserver 1.0.0.1
You should not need to restart, these changes will take effect immediately, but if you want, you can still do it.
Stormchaser,
Thanks very much for your help. Those links were super useful. Yes, DNS wasn’t working. But that’s because something more basic wasn’t working, forwarding of packets outside of my LAN. And that’s because when I moved locations, I moved from one LAN to another. The dhcp config file had my old gateway address. So I updated that and rebooted.
It seems like a bug in the system that I can update my static IP information, but the gateway is not updated (until I directly edited the config file).
Anyway, it is now connect, live, and shows up in the net.
Rob
Rob,
Thank you very much for your feedback, and you’re welcome! Glad that now the Shake is online and streaming!
The issue you’ve raised with the LAN DNS is a good one, and I will open a ticket for our software team so that they can take a look at this in depth and possibly, come up with a solution.
Thank you again, and enjoy shaking!