Actually, I think you have it the wrong way round and this may still be an issue: Recent piaware (from 2.1-3) and fa-supplied dump1090 have standardised on port 30104 for mlat back-feed into dump1090. So piaware was installed correctly (albeit manually by me). It is dump1090-mutability that needs to be reconfigured to make it listen on 30104 instead of the previous default of 30004.
I went off their recommendations being that dump1090-mutability1.5~dev at least in my eyes constituted āusing a different dump1090ā being it is not what is ran on their stock PiAware image. I simply used their first recommendation listed which was to reconfigure PiAware. The reason initially was due to the fact it is easier to run a command than pick through a configuration file to replace a setting.
Keep in mind I am going to have to dig into the dump1090-mutability configuration here shortly in order to deal with the lat/lon max range graph issue. When I do I will be more than happy to come back and address this at that time if that is the way we should go.
That is unless anyone sees another reason to continue to allow dump1090 beast format connections on the original port 30004.
Maybe I will leave the decision to the user at that time from within the scriptā¦
What I need to do is make dump1090-mutability listen on both 30004 and 30104 by default. Currently thatās not possible, it needs a bit of work in the code.
The idea with 30104 is that 30004 is already used by a bunch of non-mlat-aware existing installs for Beast input, so the only thing thatās safe to send there is non-mlat data. Anything listening on 30104 is assumed to be mlat-aware. But something that is mlat-aware can listen on both (30004 for backwards compatibility, 30104 to accept mlat data)
still seems this error is cropping up in the pi-aware installation of the script ā¦skippingā¦ 6a883f4 jessieās c_rehash doesnāt like multiple certificates per file ,split them and terminates the script at that point tried reinstalling twice with same result
script works fine from start to finnish if I leave pi-aware out of the install on Ubuntu 14.4
Now that you mention it, I also saw ājessieās c_rehash doesnāt like multiple certificates per file ,split themā message during my install a few days ago but the script continued seemingly fine. It did build the piaware package but did not install it. A subsequent manual installation of the package went fine.
Iāll try a fresh rebuild, but that message is the GitHub commit message that Obj used when he fixed the issue, it wasnāt added to the install script. You all are on Raspberries, correct?
Iām on Raspberry Pi B+, with Jessie. My last install was on the 5th. I did not see the, ājessieās c_rehash doesnāt like multiple certificates per file ,split themā message during the install though I did have to split the files.
no I was trying to install the script on Ubuntu 14.4 when getting ]jessieās c_rehash doesnāt like multiple certificates per file ,split them .last line after this was end it did not continue
Okay, Iāll try to set up a virtual Ubuntu x86 and see what I can find, it looks like the current script runs okay with the Raspberries, just a cursory check doesnāt reveal any problems, the Jessie message is just the one from the GitHub commit as I suspectedā¦ Iāll do a deeper dive and see what comes up.
Iām running into problems installing PiAware on Ubuntu Trusty but the problem isnāt with JPās script. Itās in the sensible-build.sh script which is flightawareās script. Iāll open an issue with that repo and see what comes up. Bash -x locks up at the git log -1 --oneline sectionā¦
Kurt, what Obj suggested was that either you use a wider terminal (yes, confirmed that does work) or hit the letter āqā on the keyboard when you get to the lock-up. (You may have to do it a second time later in the process if it locks ups with the (END).
ok thanks I will give that a try am doing all this via putty will see how wide it goes lol ,am a Linux newbe so might ask some dumb questions , this script is a godsend though for probably many like me out there
Iām not a linux noob, and I still ask dumb questionsā¦ But nothing youāve asked so far comes close to being a dumb question.
I submitted a pull request with the updated commits, (I asked jprochazka if heād accept my updates to his script), and it looks like the fixes Obj put in work fine with a small terminal size. I tried it on Ubuntu Tahir with a tiny terminal and all worked fine.
I think you can resize the terminal with Putty, but I havenāt used Putty or Kitty in a while. Finally installed cygwin and just use the terminal for everythingā¦
