Problem with installation: Port 30104 Connection (Solved)

FlightAware ADS-B Flight Tracking
1

I just set up a new Pi 2 with Raspbian Jessie, Piaware 2.1-3 and dump1090-muta v1.14. Help please.

Error in /tmp/piaware.out


10/08/2015 16:34:43 mlat(4550): Beast-format results connection with localhost:30104: [Errno 111] Connection refused

Piaware status:


dump1090 is not running.
faup1090 is running.
piaware is running.
dump1090-mutab is listening for connections on port 30005.
faup1090 is connected to port 30005.
piaware is connected to FlightAware.
dump1090-mutab is producing data on port 30005.

dump1090-muta status:


● dump1090-mutability.service - LSB: dump1090 daemon (mutability variant)
   Loaded: loaded (/etc/init.d/dump1090-mutability)
   Active: active (running) since Thu 2015-10-08 16:28:43 UTC; 8min ago
  Process: 5189 ExecStart=/etc/init.d/dump1090-mutability start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/dump1090-mutability.service
           └─5196 /usr/bin/dump1090-mutability --net --gain -10 --ppm 0 --oversample --fix --phase-enhance --lat 36.17679948407068 --lon -79.14415329694748 --max-range 225 --net-http-por...

Oct 08 16:28:43 raspberrypi systemd[1]: Started LSB: dump1090 daemon (mutability variant).
2

Check the piaware 2.1-3 thread. The standard port for back-feeding mlat positions to dump1090 has changed. Best to reconfigure your dump1090-mutability and specify beast listening port 30104 instead of (old) default of 30004.

3

As this is all new, you should really set up and use v1.15~dev. It is mlat-aware and shows nice flags:)
http://discussions.flightaware.com/post177419.html#p177419

4

:blush: Missed this: post181696.html

Solved now. Thanks!

5

Thanks. Your tutorial looks good, but there are too many additions and modifications to the system for my liking. I will stick with with v1.14 until OBJ releases a final v1.15 package.

6

No problem. But the thing with v1.14 is that it will pass on any mlat positions that it receives on 30104 as regular ADSB positions on port 30005. This may or may not be a problem, depending what else you are feeding from that instance of dump1090. Some other software and/or sharing sites may not like the mix of mlat and ADSB positions and complain about it. That’s why it’s best to use latest FA-supplied dump1090 or mutability v1.15~dev. Both are mlat-aware and will by default NOT forward mlat positions in their 30005 output.

7

Thanks for the explanation. I may have read that before but completely understood it. I do also feed FR24 and PlaneFinder. I’ll switch to either FA dump or see about building 1.15.

8

So I’m getting around to building dump1090-mutability v1.15~dev. What’s the best way to go about changing from version 1.14 to 1.15? Is it necessary to ‘dpkg --remove dump1090-mutability’ before installing v1.15?

9

You don’t have to remove the 1.14 version. Just install 1.15 and it will take care of upgrading.

10

The upgrade went perfectly. Thanks!