Log and halt questions


#1

First, I got an email notice that my secondary feeder was not sending. My secondary feeder is a Raspberry Pi3. It has halted a couple of times. My other one, which is an earlier model of Raspberry has never halted as far as I know. When I say halted, I don’t think it is the device that halted but the feed that halted for some reason. Trying to get some clues on what is going on, I tried looking at the log. Copying the log from there is an excercise in frustration. Just when I’m highlighting most of it, it refreshes. I suppose the same log is available directly from my RP, but where? If there’s another way to download the log, what is that?

Having said that, can anyone tell from the log what may have happened to stop the feed? The fact the log was still being updated shows that the device was still running - just not connecting properly. In case the log gets outdated before people get a chance to look at it, here is a portion I was able to copy. dropbox.com/s/1v9hqepn3tth1 … g.rtf?dl=0

P.S. I restarted it 15 minutes ago or so, and it’s running fine now.


#2

404 on your logs.

piaware logs are available at /var/log/piaware.log (3.0) or /tmp/piaware.out (older versions)


#3

Here’s a snippet, during the time it was failing. If I’m reading it right, it looks like one of the programs used may have abended so was not responding. Does that sound right?

[2016-08-21 09:29 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:29 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:29 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:30 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:30 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:30 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:30 CDT] no ADS-B data program seen listening on port 30005 for 310 seconds, next check in 60s
[2016-08-21 09:30 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:30 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:30 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:31 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:31 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:31 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:31 CDT] no ADS-B data program seen listening on port 30005 for 370 seconds, trying to start it…
[2016-08-21 09:31 CDT] attempting to start fadump1090.sh using ‘invoke-rc.d fadump1090.sh start’…
[2016-08-21 09:31 CDT] dump1090 start appears to have been successful
[2016-08-21 09:31 CDT] mlat(2631): Receiver status: disconnected
[2016-08-21 09:31 CDT] mlat(2631): Server status: not synchronized with any nearby receivers
[2016-08-21 09:31 CDT] mlat(2631): Receiver: 0.0 msg/s received 0.0kB/s from receiver
[2016-08-21 09:31 CDT] mlat(2631): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
[2016-08-21 09:31 CDT] mlat(2631): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used
[2016-08-21 09:31 CDT] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2016-08-21 09:31 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:31 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:31 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:32 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:32 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:32 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:32 CDT] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2016-08-21 09:32 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:32 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:32 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:32 CDT] 10819679 msgs recv’d from dump1090 (0 in last 5m); 10799756 msgs sent to FlightAware
[2016-08-21 09:33 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:33 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:33 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:33 CDT] no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
[2016-08-21 09:33 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:33 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:33 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:34 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:34 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:34 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:34 CDT] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
[2016-08-21 09:34 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:34 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:34 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:35 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:35 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:35 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:35 CDT] no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
[2016-08-21 09:35 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:35 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:35 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:36 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:36 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:36 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:36 CDT] no ADS-B data program seen listening on port 30005 for 310 seconds, next check in 60s
[2016-08-21 09:36 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:36 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:36 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:37 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:37 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:37 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:37 CDT] no ADS-B data program seen listening on port 30005 for 370 seconds, trying to start it…
[2016-08-21 09:37 CDT] attempting to start fadump1090.sh using ‘invoke-rc.d fadump1090.sh start’…
[2016-08-21 09:37 CDT] dump1090 start appears to have been successful
[2016-08-21 09:37 CDT] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2016-08-21 09:37 CDT] 10819679 msgs recv’d from dump1090 (0 in last 5m); 10799756 msgs sent to FlightAware
[2016-08-21 09:37 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:37 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:37 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:38 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:38 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2016-08-21 09:38 CDT] mlat(2631): Reconnecting in 30.0 seconds
[2016-08-21 09:38 CDT] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2016-08-21 09:38 CDT] mlat(2631): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2016-08-21 09:38 CDT] mlat(2631): Connection to localhost:30005 lost: [Errno 111] Connection refused


#4

dump1090 has crashed and doesn’t seem to be restarting.

I suggest you try with a piaware 3 image as it is much better about capturing logs.


#5

I’m planning to do that next weekend, when, hopefully, we’re not under a perpetual flash flood watch/warning. The issue is the traction on my relatively steep roof when it’s wet.


#6

Are you running your raspberry pi off of Wi-Fi. Is it more than 10 feet from your router, or through a wall or two? If it is, try running a ping test and make sure you aren’t getting packet loss. That can definitely cause the issues you describe. To run the test, SSH into your pie and type the following…

Ping “ip address of your router”

Let that run for a solid minute and then press Cntrl ^ C to cancel. If your packet loss is anything more than 1 to 2%, I would consider moving your raspberry pi closer to your router, or running an ethernet cable.

For some reason packet loss causes terrible data connection and will disconnect you from the server in a heartbeat.

I have also found that the raspberry pies Wi-Fi can be questionable at best. It seems to operate very well close to the router, but if you get more than 10 feet or a wall or two away sometimes they have issues.

Sent from my iPhone using Tapatalk


#7

wifi issues would not cause dump1090 to exit.


#8

Oops. I figured a high ping loss could cause an issue. I have had similar issues when using darkice audio streaming on a Pi. Thought it could have been an issue here.

My apologies.