"unknown process" issue ?!

So I’m reading about the upgrade to 6.0, and the grey gear icon, and I see the recent logs (yeah I’m a set it and forget it mostly on these things), and I notice there are several entries of
Started faup978 (pid 21936) to connect to unknown process and
0 msgs recv’d from unknown process; 0 msgs sent to FlightAware and

[2021-09-04 04:35 EDT] ADS-B data program ‘unknown process’ is listening on port 30978, so far so good
[2021-09-04 04:35 EDT] Starting faup978: /usr/lib/piaware/helpers/faup978 --connect localhost:30978
[2021-09-04 04:35 EDT] 1 msgs recv’d from unknown process (0 in last 5m); 0 msgs sent to FlightAware
[2021-09-04 04:35 EDT] 6514783 msgs recv’d from dump1090-fa (86 in last 5m); 6514145 msgs sent to FlightAware
[2021-09-04 04:37 EDT] faup978(20451): connection to [::1]:30978 failed: Connection timed out
[2021-09-04 04:39 EDT] faup978(20451): connection to 127.0.0.1:30978 failed: Connection timed out
[2021-09-04 04:39 EDT] faup978 exited normally
[2021-09-04 04:39 EDT] lost connection to unknown process via faup978
[2021-09-04 04:39 EDT] reconnecting to unknown process
[2021-09-04 04:39 EDT] faup978(20451): Connection failed: Connection timed out
[2021-09-04 04:39 EDT] Starting faup978: /usr/lib/piaware/helpers/faup978 --connect localhost:30978
[2021-09-04 04:39 EDT] faup978(20498): Connecting to localhost:30978
[2021-09-04 04:39 EDT] Started faup978 (pid 20498) to connect to unknown process
[2021-09-04 04:39 EDT] ADS-B data program ‘unknown process’ is listening on port 30978, so far so good

which are all before updating, and then the following afterwards…

[2021-09-04 04:58 EDT] Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 206.253.84.195:10234:1122709680
[2021-09-04 04:58 EDT] adept reported location: 35.74998, -80.52060, 880ft AMSL
[2021-09-04 04:58 EDT] mlat-client(21926): Listening for Extended Basestation-format results connection on port 30106
[2021-09-04 04:58 EDT] ADS-B data program ‘unknown process’ is listening on port 30978, so far so good
[2021-09-04 04:58 EDT] mlat-client(21926): Listening for Beast-format results connection on port 30105
[2021-09-04 04:58 EDT] mlat-client(21926): fa-mlat-client 0.2.11 starting up
[2021-09-04 04:58 EDT] Started faup1090 (pid 21933) to connect to dump1090-fa
[2021-09-04 04:58 EDT] mlat-client(21926): Input format changed to BEAST, 12MHz clock
[2021-09-04 04:58 EDT] ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good
[2021-09-04 04:58 EDT] mlat-client(21926): Route MTU changed to 1500
[2021-09-04 04:58 EDT] Starting faup978: /usr/lib/piaware/helpers/faup978 --connect localhost:30978
[2021-09-04 04:58 EDT] mlat-client(21926): Using UDP transport to 206.253.84.195 port 10234
[2021-09-04 04:58 EDT] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 35.750 --lon -80.521
[2021-09-04 04:58 EDT] Started faup978 (pid 21936) to connect to unknown process
[2021-09-04 04:58 EDT] faup978(21936): Connecting to localhost:30978
[2021-09-04 04:58 EDT] mlat-client(21926): Input connected to localhost:30005
[2021-09-04 04:58 EDT] mlat-client(21926): Beast-format results connection with ::1:30104: connection established
[2021-09-04 04:59 EDT] 0 msgs recv’d from unknown process; 0 msgs sent to FlightAware
[2021-09-04 04:59 EDT] 21 msgs recv’d from dump1090-fa; 21 msgs sent to FlightAware

Have two dongles connected, powered by a 12vdc to 5vdc converter off a 10 amp power supply, two antenna’s, and apparently I’ve botched SOMETHING in the config somewhere (as usual)

Any idea (looking at you ABCD567 haha) what/where/how I’ve done wrong?

Thanks for any ideas, I’ll try to reply with whatever info you ask for as quick as I can

Gary

Is this a PiAware sdcard or something else?

SD card on pi fresh image 14 Aug, last card died… at the beginning I’d swear it said everything was fine, so I stopped checking everything…

G

Right, but is this a PiAware sdcard image or some other image with a package install?

The “unknown process” implies that sudo (or netstat) isn’t working right; the “connection timed out” in earlier logs implies that there’s something wrong with networking. Neither should happen on a piaware sdcard image.

If this is a piaware sdcard image I would suggest recording your config then reimaging.

it’s a piaware image from this website.

The “connection timed out” section you’re talking about is internal IP address connection to the internal port

[2021-09-04 04:37 EDT] faup978(20451): connection to [::1]:30978 failed: Connection timed out
[2021-09-04 04:39 EDT] faup978(20451): connection to 127.0.0.1:30978 failed: Connection timed out

It looks like the [::1] is trying to reference IPv6, while obviously 127.0.0.1:30978 is IPv4

For some reason faup978 isn’t communicating with the rest of the program for some unknown reason, but the 1090 is working fine…

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.