Something crashes/fails every week or so


#1

Hi,

Over the past few months, my PiAware seem to be stuck in a state where the different components stop talking to each other about once a week. Restarting the different services doesn’t fix it, but a reboot always does.

Here are my stats when in this state earlier today:

============================================================
pi@piaware ~ $ piaware -v
3.5.3

pi@piaware ~ $ dump1090-fa --help

| dump1090 ModeS Receiver dump1090-fa v3.5.3~bpo8+1 |

build options: ENABLE_RTLSDR

pi@piaware ~ $ sudo piaware-config
allow-auto-updates yes # value set at /boot/piaware-config.txt:5
allow-manual-updates yes # value set at /boot/piaware-config.txt:4
image-type piaware # value set at /boot/piaware-config.txt:6
mlat-results-format “beast,connect,localhost:30104 basestation,listen,12345” # value set at /boot/piaware-config.txt:7

pi@piaware ~ $ piaware-status
PiAware master process (piaware) is running with pid 2284.
PiAware ADS-B client (faup1090) is running with pid 12171.
PiAware mlat client (fa-mlat-client) is running with pid 15661.
Local ADS-B receiver (dump1090-fa) is running with pid 13084.

dump1090-fa (pid 13084) is listening for connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is connected to FlightAware.

dump1090 is NOT producing data on localhost:30005.

Your feeder ID is ad723f66-e7fd-43e0-9828-a9aa1a4f2ae8 (from /var/cache/piaware/feeder_id)

I’ve uploaded the whole /var/log/piaware.log to here: https://1drv.ms/u/s!AlUorSoxzp3ujSXMwXoKFvVzdPIF

Here are some maybe relevant lines:

2017-12-30 01:55:19Z no new messages received in 3766 seconds, it might just be that there haven’t been any aircraft nearby but I’m going to try to restart everything, just in case…
2017-12-30 01:55:20Z faup1090 exited with SIG SIGHUP
2017-12-30 01:55:20Z attempting to restart dump1090…
2017-12-30 01:55:21Z attempting to restart dump1090-fa using ‘invoke-rc.d dump1090-fa restart < /dev/null &’…
2017-12-30 01:55:21Z dump1090 restart appears to have been successful
Stopping dump1090-fa server: dump1090-fa.
2017-12-30 01:55:21Z mlat-client(5702): Lost connection to localhost:30005
2017-12-30 01:55:21Z mlat-client(5702): Reconnecting in 30.0 seconds
2017-12-30 01:55:21Z mlat-client(5702): Beast-format results connection with 127.0.0.1:30104: connection lost
Starting dump1090-fa server: dump1090-fa02017-12-30 01:55:31Z ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good
2017-12-30 01:55:31Z Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 47.494 --lon -122.464
2017-12-30 01:55:31Z Started faup1090 (pid 13237) to connect to dump1090-fa
2017-12-30 01:55:51Z 1227805 msgs recv’d from dump1090-fa (0 in last 5m); 1218880 msgs sent to FlightAware
2017-12-30 01:55:51Z mlat-client(5702): Beast-format results connection with ::1:30104: [Errno 97] Address family not supported by protocol

Is this a known problem?

Thanks,

David

PS: This new message board software seems to be a step backwards.


#2

No, it is not backwards, It is different.
Only a simple thing when posting code: place 3 grave-accents ``` above and below the code. The grave-accent key is left of number 1 key on US keyboard. Please see image below

.
TYPED
post code using ``` -Typed

APPEARS

post code using ``` - Appear

.

I have added 3 grave-accents ``` to the code part your quoted post below. See how nice it looks now!


#3

Thanks for fixing the formatting and this very useful tip. I was looking over the available editing tools:

toolbar

and didn’t see any way to change fonts to a fixed one, add indents, tables, shading, etc. It looked like my only choices were Bold & Italic. I was considering writing my post in Word, saving as .html, and pasting it in case that worked, but it just seemed a bit overkill.

It would be nice if the triple accent grave trick was discoverable via the compose toolbar. I did search in the thread on the new forum software for ‘font’ and found no hits.

Anyway, regarding my PiAware problem, as I said it is fixed with a device reboot but not a service restart. On Windows when a process Access Violates and dies, there is a .dmp file to debug. Does Linux have anything analogous that I can look for in case something is AV’ing?

Thanks,

David


#6

Please see this thread which I have created today:

How To Format Messages in This Discussion Forum


#7

Yes, I saw that. Thanks. It would be good if the FlightAware folks could make it a ‘sticky’ topic – if that concept exists anymore.

I’m still hoping someone will be able to address the actual issue I’m hitting. I suppose I could create some kind of cron job to reboot the PI in the middle of every night, but it would be good to find out what state it gets into and why it gets into that state.

David