Losing Connection but Still Connected


#1

Folks,

I’m going round in circles here, got a Pi Zero that has been running without issue for many months but of late has suddenly stopped giving Skyview or connecting to FA

With a few script files running I now know the Pi is still running when this occurs, it shows as still connected to my WiFi but I am unable to ssh in to it.

Checking the PiAware log it seems I suddenly am unable to contact other devices on the internet/network.

Below is small section of log file at time of failure;

Blockquote

Jan 12 10:48:19 zero piaware[624]: mlat-client(9580): Server status: synchronized with 302 nearby receivers
Jan 12 10:48:19 zero piaware[624]: mlat-client(9580): Receiver: 182.2 msg/s received 32.3 msg/s processed (18%)
Jan 12 10:48:19 zero piaware[624]: mlat-client(9580): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.3kB/s UDP to server
Jan 12 10:48:19 zero piaware[624]: mlat-client(9580): Results: 11.9 positions/minute
Jan 12 10:48:19 zero piaware[624]: mlat-client(9580): Aircraft: 8 of 13 Mode S, 16 of 18 ADS-B used
Jan 12 10:48:48 zero piaware[624]: 161305 msgs recv’d from dump1090-fa (644 in last 5m); 161236 msgs sent to FlightAware
Jan 12 10:53:48 zero piaware[624]: 161980 msgs recv’d from dump1090-fa (675 in last 5m); 161911 msgs sent to FlightAware
Jan 12 10:57:04 zero piaware[624]: data isn’t making it to FlightAware, reconnecting…
Jan 12 10:57:04 zero piaware[624]: multilateration data no longer required, disabling mlat client
Jan 12 10:57:05 zero piaware[624]: fa-mlat-client exited normally
Jan 12 10:57:05 zero piaware[624]: reconnecting in 55 seconds…
Jan 12 10:57:05 zero piaware[624]: mlat-client(9580): Disconnecting from localhost:30005: Lost connection to multilateration server, no need for input data
Jan 12 10:57:05 zero piaware[624]: mlat-client(9580): Exiting on connection loss
Jan 12 10:58:00 zero piaware[624]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jan 12 10:58:20 zero piaware[624]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn’t open socket: Name or service not known
Jan 12 10:58:20 zero piaware[624]: reconnecting in 49 seconds…
Jan 12 10:58:50 zero piaware[624]: 162586 msgs recv’d from dump1090-fa (606 in last 5m); 162324 msgs sent to FlightAware
Jan 12 10:59:09 zero piaware[624]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jan 12 10:59:29 zero piaware[624]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn’t open socket: Name or service not known
Jan 12 10:59:29 zero piaware[624]: reconnecting in 62 seconds…
Jan 12 11:00:31 zero piaware[624]: Connecting to FlightAware adept server at 70.42.6.224/1200
Jan 12 11:00:34 zero piaware[624]: Connection to adept server at 70.42.6.224/1200 failed: host is unreachable
Jan 12 11:00:34 zero piaware[624]: reconnecting in 67 seconds…

Other devices connected to the same access point appear to be working fine.

Any pointers appreciated as I am baffled here.

Geffers


#2

There might be some information in the “dmesg” or the “/var/log/syslog” about why the wifi connection is failing. But this looks more like a wifi hardware problem in the RPi Zero.

There is one fairly easy way to rule out or confirm the hardware problem by using an external USB wifi adapter.

Since you are using a RPi zero you would need to use a USB hub with an external USB wifi adapter OR disconnect the prostick for the external USB wifi adapter during the test.
You can disable the internal Raspberry Pi Zero wifi adapter by setting rfkill to yes.

piaware-config rfkill yes

With rfkill on, piaware’s boot system will look for any connected wifi USB adapters and setup with the same ssid and password you have in your piaware configuration on the wifi adapter.

You can go back to the internal wifi connection by turning rfkill back to no.


#3

I’ve tried the same card in a Pi3 and had the same problem. Trouble is it is spasmodic so difficult to narrow down.

I’m actually thinking it is a DNS issue, I am experimenting with an advert filter running on a separate Raspberry Pi which acts as a DNS server. I may be causing an unknowing conflict somewhere.

Geffers