fadump1090 appears to have stopped and won't restart


#1

I have been running piaware on a RPi with the SD Card version 1.20 for some time now. It had been running continuously, unattended for over 10 days, successfully feeding data to FA and displaying aircraft on dump1090 browser display…until today. Today in needed to swap out the WIFI dongle so I connected on SSH via WIFI and did a “sudo shutdown -h now” after which I unplugged the system. After replacing the dongle I restarted the system and successfully re-established an SSH connection. Much to my surprise and dismay when I ran piaware-status I got the results below indicating dump1090 wasn’t running. Also, there was no browser display from the dump1090 server. The SDR appears to be on (blue light). I have tried numerous times to start the dump1090 (sudo /etc/init.d/fadump1090.sh start), unsuccessfully. The FA ADS-B Feeder Statistics Log indicated FA had tried sending a start command as well, but indicated it was successful…even though the output results were/are negative. (See log below)

I’m not looking forward to the prospect of re-installing 1.20 from scratch and setting everything up again, so I’m hoping someone out there has a suggestion. I wish I were more of a Linux guru…but I’m not. I would gladly provide any additional info that might help in diagnosing the situation. Sure would be grateful for your assistance.

Thanks,
Dave K4DPF


pi@piaware ~ $ sudo piaware-status
dump1090 is not running.
faup1090 is not running.
piaware is running.
no program appears to be listening for connections on port 30005.
no program appears to be listening for connections on port 10001.
piaware is NOT connected to port 10001.
piaware is connected to FlightAware.
got 'couldn’t open socket: connection refused’
maybe dump1090 is NOT producing data on port 30005.
got 'couldn’t open socket: connection refused’
maybe dump1090 is NOT producing data on port 10001.

FA Log excerpt:
[2015-04-18 18:50 EDT] no new messages received in 3600 seconds, it might just be that there haven’t been any aircraft nearby but I’m going to try to restart dump1090, possibly restart faup1090 and definitely reconnect, just in case…
[2015-04-18 18:50 EDT] attempting to restart dump1090 using ‘/etc/init.d/fadump1090.sh restart’…
[2015-04-18 18:50 EDT] dump1090 restart appears to have been successful
[2015-04-18 18:50 EDT] stop_faup1090: no need to stop faup1090, it’s not running
[2015-04-18 18:50 EDT] close_faup1090_socket called with no socket argument and no faup1090 global socket
[2015-04-18 18:50 EDT] will attempt to connect to faup1090 in 60s…
[2015-04-18 18:50 EDT] 0 msgs recv’d from (not currently connected to an adsb source) (0 in last 5m); 0 msgs sent to FlightAware
[2015-04-18 18:51 EDT] no ADS-B data program is serving on port 30005, next check in 60s


#2

Do you have a backup of the image?


#3

Regrettably, all I have is the original image I downloaded from FA. :blush:


#4

there should be a log from dump1090 saying why it can’t start - have a look in /var/log (that’s where I’d expect to find it).

My Pi is running on a Vonets VAP11G WiFi Bridge Dongle - it takes power from a USB port (on the Pi) and plugs into the Pi ethernet port … no wifi setup on the PI just plug it in.

Use a windows PC to set the dongle for SSID & Password.


#5

Thanks, PeterHR, will check the log when I get back from church.
Dave


#6

Below is a dir of the /var/log directory. I didn’t notice anything related to dump1090 in there.

Thanks, Dave


pi@piaware /var/log $ dir
alternatives.log debug kern.log.1 regen_ssh_keys.log
alternatives.log.1 debug.1 kern.log.2.gz samba
apt debug.2.gz kern.log.3.gz syslog
auth.log debug.3.gz kern.log.4.gz syslog.1
auth.log.1 debug.4.gz lastlog syslog.2.gz
auth.log.2.gz dmesg lpr.log syslog.3.gz
auth.log.3.gz dmesg.0 mail.err syslog.4.gz
auth.log.4.gz dmesg.1.gz mail.info syslog.5.gz
bootstrap.log dmesg.2.gz mail.log syslog.6.gz
btmp dmesg.3.gz mail.warn syslog.7.gz
btmp.1 dmesg.4.gz messages user.log
ConsoleKit dpkg.log messages.1 user.log.1
daemon.log dpkg.log.1 messages.2.gz user.log.2.gz
daemon.log.1 faillog messages.3.gz user.log.3.gz
daemon.log.2.gz fontconfig.log messages.4.gz user.log.4.gz
daemon.log.3.gz fsck news wtmp
daemon.log.4.gz kern.log ntpstats wtmp.1


#7

Well, I bit the bullet and rebuilt the piaware image from scratch. After changing passwords and setting up for WIFI I attempted to learn from my mistake and do an image backup with Image Writer. Unfortunately, after about 16% process completion I got an error message indicating there was a data error, cycle redundancy. The error repeated on a different machine as well. So that’s a problem to be resolved.

For the moment the software is working and sending reports to Flight Aware… So I’m happy …for the moment:-)

Thanks for the suggestions…

Dave K4DPF


#8

I have been having issues with PiAware crashing and trying to get to the bottom of the problem and not quite understanding what and why it is crashing. I have looked at the /var/log/syslog file to identify what is happening and I think the issue may be because of some of the info in the lines below:




May 25 06:58:16 time systemd[1]: Started LSB: fadump1090 initscript.
May 25 07:03:39 time systemd[1]: Stopping LSB: fadump1090 initscript...
May 25 07:03:39 time fadump1090.sh[18829]: Stopping dump1090 server: dump1090/sbin/start-stop-daemon: warning: failed to kill 4974: No such process
May 25 07:03:39 time fadump1090.sh[18829]: .
May 25 07:03:39 time systemd[1]: Starting LSB: fadump1090 initscript...
May 25 07:03:39 time fadump1090.sh[18838]: Starting dump1090 server: dump10900
May 25 07:03:39 time systemd[1]: Started LSB: fadump1090 initscript.
May 25 12:55:46 time systemd[1]: Starting Cleanup of Temporary Directories...
May 25 12:55:46 time systemd[1]: Started Cleanup of Temporary Directories.
May 25 15:42:19 time systemd[1]: Started LSB: fadump1090 initscript.
May 25 15:48:30 time systemd[1]: Started LSB: fadump1090 initscript.
.
.
.
May 25 22:11:19 time systemd[1]: Started LSB: fadump1090 initscript.
May 25 22:12:44 time systemd[1]: Stopping LSB: fadump1090 initscript...
May 25 22:12:44 time fadump1090.sh[26200]: Stopping dump1090 server: dump1090/sbin/start-stop-daemon: warning: failed to kill 18846: No such process
May 25 22:12:44 time fadump1090.sh[26200]: .
May 25 22:12:44 time systemd[1]: Starting LSB: fadump1090 initscript...
May 25 22:12:44 time fadump1090.sh[26210]: Starting dump1090 server: dump10900
May 25 22:12:44 time systemd[1]: Started LSB: fadump1090 initscript.
May 26 02:57:56 time systemd[1]: Started LSB: fadump1090 initscript.
.
.
.
May 26 08:06:40 time systemd[1]: Started LSB: fadump1090 initscript.
May 26 08:12:39 time systemd[1]: Stopping LSB: fadump1090 initscript...
May 26 08:12:39 time fadump1090.sh[31781]: Stopping dump1090 server: dump1090/sbin/start-stop-daemon: warning: failed to kill 26217: No such process
May 26 08:12:39 time fadump1090.sh[31781]: .
May 26 08:12:39 time systemd[1]: Starting LSB: fadump1090 initscript...
May 26 08:12:39 time fadump1090.sh[31790]: Starting dump1090 server: dump10900
May 26 08:12:39 time systemd[1]: Started LSB: fadump1090 initscript.
May 26 08:23:49 time systemd[1]: Starting Session c5 of user pi.
May 26 08:23:49 time systemd[1]: Started Session c5 of user pi.



There were MANY lines that were consecutive lines with only the time being different that ended with “systemd[1]: Started LSB: fadump1090 initscript.” For these redudant lines, I put in a few dots, so as not to fill the screen with redundant data, so in reading, just know if you see a line with a “.” it means several lines of the same thing with different times. My guess is that my crash has something to do with the lines such as “fadump1090.sh[31781]: Stopping dump1090 server: dump1090/sbin/start-stop-daemon: warning: failed to kill 26217: No such process.” The machine itself doesn’t crash but the PiAware program does. I am able to log into the PiAware and restart it with “sudo /etc/init.d/fadump1090.sh restart”.