faup1090 and piaware are down, can't figure out why

FlightAware ADS-B Flight Tracking
1

I’ve built an aggregator pi and have finally managed to serve up a merged feed to adsbexchange.com and FR24. However, for some reason piaware does not start.
I’ve tried trouble shooting but have made little progress thus far. Here is the output of piaware-status



~$ sudo piaware-status
dump1090 is not running.
faup1090 is not running.
piaware is not running.
dump1090-mutabi is listening for connections on port 30005.
faup1090 is NOT connected to port 30005.
piaware is NOT connected to FlightAware.
dump1090-mutabi is producing data on port 30005.

…and output of ps:


~$ ps auxww | grep dump1090
dump1090   277  1.2  0.4   4484  3108 ?        S    13:52   0:51 /usr/bin/dump1090-mutability --net-only --ppm 0 --oversample --fix --phase-enhance --lat xx.xxxx --lon yy.yyyy --max-range 500 --net-http-port 8080 --net-ri-port 30001 --net-ro-port 30002 --net-bi-port 30004 --net-bo-port 30005 --net-sbs-port 30003 --net-fatsv-port 10001 --net-heartbeat 60 --net-ro-size 500 --net-ro-interval 1 --net-buffer 2 --stats-every 3600 --write-json-every 1 --json-location-accuracy 1 --quiet

As you see mutability is up and running so the error “dump1090 is not running” can be ignored. Can anyone assist with where I should be looking please?

Many thanks

2

Did you try a


sudo reboot
3

yes

4

Did you make any changes to anything. A friend of mine has kind of the same issue and he put in the wrong password for FA.

sudo piaware-config -user (Username) -password

5

I had to completely rebuild my pi as it crashed crashed due to rather rash scripting skills.

I’ve supplied the username and password again - no joy.

6

did you have already changed the piaware (2.13?) port to where mutability is set to - or vice versa? e.g.


$ sudo piaware-config -mlatResultsFormat beast,connect,localhost:30004
$ sudo service piaware restart
7

First thing to try is to start the piaware init.d script manually:



$ sudo service piaware start

If piaware is OK after that then you have a problem with your rc.d configuration and piaware is not getting started on boot.

If that doesn’t help, look at the piaware logs in /tmp/piaware.out

If the logs don’t help, try starting piaware in the foreground (it will log to your shell):



$ sudo piaware -debug
8

Thank you obj and TomMuc.

Before trying to restart piaware manually through the init.d script I deleted the piaware.out log, rebooted and then checked the piaware status:


 piaware.service - LSB: Communicate ADS-B data to FlightAware
   Loaded: loaded (/etc/init.d/piaware)
   Active: active (exited) since Sun 2015-10-18 21:14:24 IST; 8min ago
  Process: 226 ExecStart=/etc/init.d/piaware start (code=exited, status=0/SUCCESS)

Oct 18 21:14:24 aggregator piaware[226]: Starting piaware server: piaware.

I also checked the piaware.out log and it shows:



10/18/2015 15:44:40 ****************************************************
10/18/2015 15:44:40 piaware version 2.1-3 is running, process ID 252
10/18/2015 15:44:40 your system info is: Linux aggregator 4.2.3-2-osmc #1 SMP PREEMPT Mon Oct 12 01:58:40 UTC 2015 armv7l GNU/Linux
10/18/2015 15:44:40 connecting to FlightAware piaware.flightaware.com/1200
10/18/2015 15:44:42 FlightAware server SSL certificate validated
10/18/2015 15:44:42 encrypted session established with FlightAware
couldn't execute "ip": no such file or directory
    while executing
"open $cmd $mode"
    (procedure "open_nolocale" line 5)
    invoked from within
"open_nolocale "|ip address show dev $dev""
    (procedure "get_local_device_ip_address" line 2)
    invoked from within
"get_local_device_ip_address $iface"
    (procedure "get_default_gateway_interface_and_ip" line 14)
    invoked from within
"get_default_gateway_interface_and_ip gateway iface ip"
    (object "::adept" method "::fa_adept::AdeptClient::login" body line 25)
    invoked from within
"login"
    (object "::adept" method "::fa_adept::AdeptClient::connect" body line 63)
    invoked from within
"adept connect"
    (procedure "main" line 82)
    invoked from within
"main $argv"
    invoked from within
"if {!$tcl_interactive} {
    main $argv
}"
    (file "/usr/lib/piaware/main.tcl" line 125)
    invoked from within
"source /usr/lib/piaware/main.tcl"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 source $path"
    from tcllauncher running "piaware -p /var/run/piaware.pid"

The part that looks suspect is where it begins by saying: “couldn’t execute ip…”

I then executed the piaware service and it returned nothing - just the prompt

On looking up the piaware.out file again it does not show up any additional information.

I executed piaware in debug mode and the output is similar to the one above, its the same part that looks suspect.

You mentioned that there could be a problem with the rc.d configuration, how do I debug that? Or is the “couldn’t find ip” the culprit?

9

I guess this is a raspbian jessie install that you’ve built yourself.

Try installing the iproute package.

(raised an issue for this: github.com/flightaware/piaware/issues/25)

10

hi clipsnotebook,

sorry - my knowledge isn’t good enough to identify the problem out of the logfiles - but i’m sure obj as the developer of piaware can :slight_smile:
what i’ve learned some weeks ago when starting with ads-b was - that the fr24 software is very egoistic and seems to violate some other apps.

so - maybe a fresh install with piaware first could be a chance to find the problem. if the fresh install works you could then install the other feeds and look every time if it still works.

the best way to install fr24 feed with other feeds - mgunther has a how to: http://discussions.flightaware.com/post182043.html#p182043

11

obj - That was brilliant! Thank you! Its all up and running.

TomMuc - I read about that issue earlier and was aware of it. Therefore, I installed piaware before FR24. Thanks to you as well.

:slight_smile: