Hello, this is driing me a bit crazy as I unable to find out exactly whats happening. System (PI 5 w/ 10.2 image / dhcp to a Ubiquiti UniFi Dream Machine Pro) will run for a day or just a few hours and these errors show up:
timed out waiting for alive message from FlightAware, reconnecting...
Connection to adept server at piaware.flightaware.com/1200 failed: couldn't open socket: Temporary failure in name resolution
It reconnects but odds are it will fail again within a few minutes, though sometimes it will then run for 5 or 6 hours or more.
These are also annoying:
Aug 25 11:38:26 piaware piaware[5174]: NOTICE from adept server: 11% of multilateration messages (UDP) are not reaching the server - check your network?
If anyone has seen this or has any suggestions on what to look for it would be appreciated.
Bob
Aug 25 11:10:32 piaware piaware[754]: mlat-client(1534): Beast-format results connection with ::1:30104: connection established
Aug 25 11:11:43 piaware piaware[754]: timed out waiting for alive message from FlightAware, reconnecting...
Aug 25 11:11:43 piaware piaware[754]: multilateration data no longer required, disabling mlat client
Aug 25 11:11:44 piaware piaware[754]: fa-mlat-client exited normally
Aug 25 11:11:44 piaware piaware[754]: reconnecting in 5 seconds...
Aug 25 11:11:44 piaware piaware[754]: mlat-client(1534): Disconnecting from localhost:30005: Lost connection to multilateration server, no need for input data
Aug 25 11:11:44 piaware piaware[754]: mlat-client(1534): Exiting on connection loss
Aug 25 11:11:49 piaware piaware[754]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Aug 25 11:11:59 piaware piaware[754]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn't open socket: Temporary failure in name resolution
Aug 25 11:11:59 piaware piaware[754]: reconnecting in 5 seconds...
Aug 25 11:12:04 piaware piaware[754]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Aug 25 11:12:10 piaware piaware[754]: Connection with adept server at piaware.flightaware.com/1200 established
Aug 25 11:12:18 piaware piaware[754]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Aug 25 11:12:18 piaware piaware[754]: FlightAware server certificate validated
Aug 25 11:12:18 piaware piaware[754]: encrypted session established with FlightAware```
This issue is often caused by firewalls blocking/dropping or perhaps some VPN or other proxy configuration.
Temporary failure in name resolution" means your device can’t translate a website’s or server’s name (like www.google.com) into its numerical IP address, which is necessary to connect to it. This often happens because of a temporary issue with your network connection, DNS server problems, or misconfigured network settings.
To fix it, try these steps: restart your router and computer, check your internet connection, switch to public DNS servers (like 8.8.8.8) if you have set other DNS servers, clear your DNS cache, or restart your network service.