Shake lost ability to connect to server

gmikefox · August 24, 2020, 4:54am

I was successful at getting the Raspberry Shake to connect initially but it seems to have lost the ability to connect to the server. The shake is listed in my router’s ipconfig (internet address 10.0.0.201) using dynamic addressing and is shown as such on rs.local. I have rebooted the modem, router, computer, and shake several times. Internet is fine to all other devices on the network. The station view shows my shake (AMRBCD3) in its proper location based on my initial connection but is now offline. I’m running Windows 10. Log file is attached. Any help would be appreciated.

RSH.RBCD3.2020-08-24T04 06 03.logs.tar (464.5 KB)

ivor · August 24, 2020, 11:52am

hello,

the log files indicate there is no connection to the internet, or at least, no connection to the DNS server (75.75.75.75) which resolved various host names, NTP servers among them. thus, the NTP daemon fails to start, which prevents data from being forwarded to the server, and the data server hostname is also not able to be resolved anyway.

check your DNS server settings, guarantee the machine is accessible and can resolve hostnames and reboot the unit.

hope this helps,

richard

gmikefox · August 24, 2020, 6:35pm

Thanks for your prompt reply. I’m not that familiar with networking, but it seems as if the shake is recognized on the network and the DNS setting (75.75.75.75) is consistent between the router and shake. I have copied information from the ipconfig below. The shake is shown at 10.10.10.201 and can be reached by the browser at that address. How do I guarantee the machine is accessible and can resolve hostnames? I pinged it (see below) and that looked OK. As I mentioned, it was able to connect to server initially with these exact settings and then lost the ability to connect when I shut it down to move it (I did shut down from the browser rather than just unplug). Thanks.

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : hsd1.ca.comcast.net
IPv4 Address. . . . . . . . . . . : 10.0.0.90
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1

C:\Users\Mike>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Mike-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.ca.comcast.net

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : hsd1.ca.comcast.net
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : FC-AA-14-9E-36-02
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.0.90(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, August 23, 2020 12:53:59 PM
Lease Expires . . . . . . . . . . : Monday, August 31, 2020 9:15:50 AM
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 75.75.75.75
75.75.76.76
NetBIOS over Tcpip. . . . . . . . : Enabled

C:\Users\Mike>arp -a

Interface: 10.0.0.90 — 0xd
Internet Address Physical Address Type
10.0.0.1 10-86-8c-69-c7-4c dynamic
10.0.0.22 6c-56-97-5c-15-39 dynamic
10.0.0.35 b2-95-75-03-5e-0f dynamic
10.0.0.51 74-d4-35-02-8d-15 dynamic
10.0.0.126 60-b6-06-05-15-04 dynamic
10.0.0.201 b8-27-eb-cc-bc-d3 dynamic
10.0.0.237 68-b5-99-36-97-c4 dynamic
10.0.0.255 ff-ff-ff-ff-ff-ff static
224.0.0.2 01-00-5e-00-00-02 static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.251 01-00-5e-00-00-fb static
224.0.0.252 01-00-5e-00-00-fc static
224.0.1.60 01-00-5e-00-01-3c static
239.255.255.250 01-00-5e-7f-ff-fa static
255.255.255.255 ff-ff-ff-ff-ff-ff static

C:\Users\Mike>ping 10.0.0.201

Pinging 10.0.0.201 with 32 bytes of data:
Reply from 10.0.0.201: bytes=32 time<1ms TTL=64
Reply from 10.0.0.201: bytes=32 time<1ms TTL=64
Reply from 10.0.0.201: bytes=32 time<1ms TTL=64
Reply from 10.0.0.201: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.201:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

ivor · August 24, 2020, 7:09pm

hi,

to test access to a DNS server from your Shake, you should log in to the Shake directly and try to ping a known website, e.g., www.google.com:

> ping www.google.com

richard

gmikefox · August 24, 2020, 11:29pm

Thanks. I logged in to the shake directly and tried to ping www.google.com as you suggested. Error msg “Temporary failure in name resolution” was the result. Log of cmd prompt session shown below. Any advice on next troubleshooting step?

C:\Users\Mike>ping myshake@rs.local
Ping request could not find host myshake@rs.local. Please check the name and try again.

C:\Users\Mike>ping rs.local

Pinging rs.local [10.0.0.201] with 32 bytes of data:
Reply from 10.0.0.201: bytes=32 time<1ms TTL=64
Reply from 10.0.0.201: bytes=32 time<1ms TTL=64
Reply from 10.0.0.201: bytes=32 time<1ms TTL=64
Reply from 10.0.0.201: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.201:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\Mike>ping www.google.com

Pinging www.google.com [216.58.194.164] with 32 bytes of data:
Reply from 216.58.194.164: bytes=32 time=33ms TTL=117
Reply from 216.58.194.164: bytes=32 time=15ms TTL=117
Reply from 216.58.194.164: bytes=32 time=12ms TTL=117
Reply from 216.58.194.164: bytes=32 time=11ms TTL=117

Ping statistics for 216.58.194.164:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 33ms, Average = 17ms

C:\Users\Mike>ssh myshake@rs.local
myshake@rs.local’s password:
Linux raspberryshake 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l

WELCOME TO RASPBERRY SHAKE!

Developed by:
Linux raspberryshake 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l

WELCOME TO RASPBERRY SHAKE!

Developed by:
Raspberry Shake: https://raspberryshake.org
Boaz Consultancy: https://sqlx.science

STATION: AM.RBCD3.00

You have mail.
Last login: Mon Aug 24 12:40:40 2020 from 10.0.0.90
myshake@raspberryshake:/opt $ ping www.google.com
ping: www.google.com: Temporary failure in name resolution
myshake@raspberryshake:/opt $

ivor · August 25, 2020, 2:05pm

hi,

two things:

log back in and see if you can ping the designated DNS server for your Pi:
> ping 75.75.75.75

if this works, then DNS server is alive, but isn’t performing its duties properly. in this case you would need to find out who is responsible for this computer and ask them why it’s not working.

if the ping to this fails, then you should investigate why your router is assigning this address as the DNS server when it’s not accessible.

also, i notice that the unit has the WiFi modules enabled, but since you’re using ethernet, this likely isn’t needed. WiFi can be disabled via the front-end config interface, but if you don’t have access to that, it can also be turned off manually by editing the file /opt/settings/user/enable-wifi.conf. change the value here to OFF and reboot.

richard

gmikefox · August 25, 2020, 9:01pm

Hi, thanks for going through this with me. I disabled the wi-fi as you suggested. When I log into the shake and ping 75.75.75.75 I get this:

WELCOME TO RASPBERRY SHAKE!

myshake@raspberryshake:/opt $ ping 75.75.75.75
PING 75.75.75.75 (75.75.75.75) 56(84) bytes of data.
From 169.254.251.58 icmp_seq=1 Destination Host Unreachable
From 169.254.251.58 icmp_seq=2 Destination Host Unreachable
From 169.254.251.58 icmp_seq=3 Destination Host Unreachable

which continues to scroll endlessly, just incrementing the seq by 1 each line. Other than the shake, there are only our two home computers plugged into our router. Both of them can ping 75.75.75.75. successfully. I had just received the shake, installed it and linked to the server successfully for a couple of days before it stopped communicating. As far as I know, no settings were changed. I don’t know if this is possible or if it would help, but could the shake be reset and reinstalled from scratch? Thanks again.

Mike Fox

gmikefox · August 27, 2020, 5:33pm

Hi
I took my shake over to my daughter’s house and tried to connect to their network. I got the same result as with my system–could not ping any outside website or the DNS server. All other computers on this network are able to do so. I am concerned that the problem is with the shake itself. Can you please advise. Thanks,

Mike Fox

ivor · August 27, 2020, 5:43pm

hi,
can you send along the log files again, and if you do this after the unit is booted, please wait some minutes before downloading them.

thanks,

richard

gmikefox · August 27, 2020, 8:40pm

Thanks for reply. Here are the log files.

Mike

RSH.RBCD3.2020-08-26T20 54 34.logs.tar (1.5 MB)

ivor · August 28, 2020, 6:03pm

hi mike,

so, this is all very strange, so instead of trying to get your DNS server 75.75.75.75 working, let’s see if we can ping any other machines.

what happens when you try to ping google, and the data server?

> ping 8.8.8.8
> ping 104.200.16.60

thanks,
richard

gmikefox · August 28, 2020, 10:39pm

Hi Richard,

I did the tests as you suggested–results are below. I also pinged the shake (10.0.0.201) from my computer’s command line and that worked fine (see below). I also logged into the shake and had it ping itself at 10.0.0.201 . I don’t know if that tells you anything but the result is shown below.

Thanks, Mike

STATION: AM.RBCD3.00

You have new mail.
Last login: Wed Aug 26 20:53:04 2020 from 10.0.0.90
myshake@raspberryshake:/opt $ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 169.254.36.160 icmp_seq=1 Destination Host Unreachable
From 169.254.36.160 icmp_seq=2 Destination Host Unreachable
From 169.254.36.160 icmp_seq=3 Destination Host Unreachable
From 169.254.36.160 icmp_seq=4 Destination Host Unreachable
From 169.254.36.160 icmp_seq=5 Destination Host Unreachable
From 169.254.36.160 icmp_seq=6 Destination Host Unreachable

STATION: AM.RBCD3.00

You have new mail.
Last login: Thu Aug 27 22:44:15 2020 from 10.0.0.90
myshake@raspberryshake:/opt $ ping 104.200.16.60
PING 104.200.16.60 (104.200.16.60) 56(84) bytes of data.
From 169.254.36.160 icmp_seq=1 Destination Host Unreachable
From 169.254.36.160 icmp_seq=2 Destination Host Unreachable
From 169.254.36.160 icmp_seq=5 Destination Host Unreachable
From 169.254.36.160 icmp_seq=6 Destination Host Unreachable

C:\Users\Mike>arp -a

Interface: 10.0.0.90 — 0xd
Internet Address Physical Address Type
10.0.0.1 10-86-8c-69-c7-4c dynamic
10.0.0.22 6c-56-97-5c-15-39 dynamic
10.0.0.35 b2-95-75-03-5e-0f dynamic
10.0.0.51 74-d4-35-02-8d-15 dynamic
10.0.0.126 60-b6-06-05-15-04 dynamic
10.0.0.201 b8-27-eb-cc-bc-d3 dynamic
10.0.0.237 68-b5-99-36-97-c4 dynamic
10.0.0.255 ff-ff-ff-ff-ff-ff static
169.254.151.196 68-b5-99-36-97-c4 dynamic
224.0.0.2 01-00-5e-00-00-02 static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.251 01-00-5e-00-00-fb static
224.0.0.252 01-00-5e-00-00-fc static
224.0.1.60 01-00-5e-00-01-3c static
239.255.255.250 01-00-5e-7f-ff-fa static
255.255.255.255 ff-ff-ff-ff-ff-ff static

C:\Users\Mike>ping 10.0.0.201

Pinging 10.0.0.201 with 32 bytes of data:
Reply from 10.0.0.201: bytes=32 time<1ms TTL=64
Reply from 10.0.0.201: bytes=32 time<1ms TTL=64
Reply from 10.0.0.201: bytes=32 time<1ms TTL=64
Reply from 10.0.0.201: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.201:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\Mike>ssh myshake@rs.local
myshake@rs.local’s password:
Linux raspberryshake 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l

WELCOME TO RASPBERRY SHAKE!

Developed by:
Raspberry Shake: https://raspberryshake.org
Boaz Consultancy: https://sqlx.science

STATION: AM.RBCD3.00

You have new mail.
Last login: Thu Aug 27 22:46:23 2020 from 10.0.0.90
STATION: AM.RBCD3.00

You have new mail.
Last login: Thu Aug 27 22:46:23 2020 from 10.0.0.90
myshake@raspberryshake:/opt $ ping 10.0.0.201
PING 10.0.0.201 (10.0.0.201) 56(84) bytes of data.
64 bytes from 10.0.0.201: icmp_seq=1 ttl=64 time=0.123 ms
64 bytes from 10.0.0.201: icmp_seq=2 ttl=64 time=0.147 ms
64 bytes from 10.0.0.201: icmp_seq=3 ttl=64 time=0.056 ms
64 bytes from 10.0.0.201: icmp_seq=4 ttl=64 time=0.075 ms
64 bytes from 10.0.0.201: icmp_seq=5 ttl=64 time=0.071 ms
64 bytes from 10.0.0.201: icmp_seq=6 ttl=64 time=0.047 ms
64 bytes from 10.0.0.201: icmp_seq=7 ttl=64 time=0.070 ms
64 bytes from 10.0.0.201: icmp_seq=8 ttl=64 time=0.088 ms
64 bytes from 10.0.0.201: icmp_seq=9 ttl=64 time=0.054 ms

gmikefox · August 29, 2020, 1:36am

Sorry, just realized I should probably send you latest log file in case you need it.

Mike

RSH.RBCD3.2020-08-28T01 51 47.logs.tar (1.8 MB)

gmikefox · September 3, 2020, 12:15am

Hi Richard,

Would it be productive to just reload the shake’s operating system and start from scratch? Alternatively, is it possible that there is a hardware problem?

Mike Fox

ivor · September 3, 2020, 2:07pm

hi mike,

i think we should try that, please download the Shake-OS image from here and burn to an SD card and try again.

i think this all points to a software issue since the problem can very easily be described as:
unit is accessible from the outside, but is unable to ping any machines on the internet

another test to try is to log in to the machine, like before, and see if you can ping other machines on your local network. this will tell us if it’s possible to ping off the unit itself.

one other thing: on your router, confirm that the WMM Wireless Configuration setting on the router is enabled, though this shouldn’t have an effect when connected to the router hard-wired.

apologies for this, we’ve not seen this particular problem before, and i can confirm that 30 other Shakes of the same type as yours have come online.

let me know if you can ping to other computers on your LAN and if a re-burned image results in any change in behavior.

cheers,

richard

gmikefox · September 3, 2020, 7:40pm

Thanks Richard,

I have tried pinging other network machines before but I verified again that you can ping the shake from another network member, but the shake cannot ping any other machine on the network. I don’t know how to confirm the WMM Wireless Configuration setting on the router, but our wireless network seems to be working just fine and there is another Raspberry Pi connected wirelessly on the network. I will go ahead and re-burn the Shake-OS. Just to be clear–to do this I should: 1) shut down the shake; 2) remove the SD card and put it in a SD reader attached to my computer; 3) download the Shake-OS image to the computer and unzip it onto the SD card. No need to reformat the card, right? I will let you know the result.

Thanks again,

Mike

gmikefox · September 4, 2020, 11:51pm

Hi Richard,

Success! Please disregard previous message. I realized that I needed to format the SD card again. Did so, reinstalled software and unit is now connected! Thank you so much for all your help. I hope moving the unit around is not a problem. I will probably carry it back and forth between Northern and Southern California occasionally.

Thanks again,

Mike Fox

ivor · September 5, 2020, 4:03pm

oh good! glad to hear that got fixed, i was beginning to lose hair… (actually, that started a while ago, but i digress)

moving the unit around is not a problem, only be sure to update the location coordinates and re-save so that the server is always up-to-date and knows where it really is.

cheers,

richard

gmikefox · September 6, 2020, 11:34pm

Thanks again Richard,

We just had a 3.4 quake near us so got to see a good signal on the helicorder! Unit still not showing on station view but I gather that sometimes it takes a while for that to happen.

Mike