Dec 31, 2015… certificate issue for mutability/librtlsdr
pi@OrangePI:~$ wget https://github.com/mutability/librtlsdr/releases/download/v0.5.4_git-1/librtlsdr0_0.5.4.git-1_armhf.deb
--2015-12-31 18:21:46-- https://github.com/mutability/librtlsdr/releases/download/v0.5.4_git-1/librtlsdr0_0.5.4.git-1_armhf.deb
Resolving github.com (github.com)... 192.30.252.129
Connecting to github.com (github.com)|192.30.252.129|:443... connected.
ERROR: The certificate of ‘github.com’ is not trusted.
ERROR: The certificate of ‘github.com’ hasn't got a known issuer.
pi@OrangePI:~$
Another issue… mutability/librtlsdr (dev)…
pi@OrangePI:~$ https://github.com/mutability/librtlsdr/releases/download/v0.5.4_git-1/librtlsdr-dev_0.5.4.git-1_armhf.deb
-bash: https://github.com/mutability/librtlsdr/releases/download/v0.5.4_git-1/librtlsdr-dev_0.5.4.git-1_armhf.deb: No such file or directory
pi@OrangePI:~$
Fix for the unknown CA is on the GitHub issues tracker. OBJ posted a commit to flightaware/piaware that splits out the certificates into two certs and the rehashes those certs, doing that manually fixes the problem. Basically, wipe out the combined cert, copy the two individual certs, rehash and restart and it’s good to go.
**Well I got some good news. I was able to get the graphs to work on the Orange Pi. So far I got it to work on the following.
**
Raspbian_For_OrangePi_PC_v0_8_0
Kali 2.0
I’m not sure if it’s the right way to do it. But maybe this is a start to fix the issue. I had to run the
sudo ./install command with sudo su privilege
Also I noticed that putting in the IP address of the Orange Pi in the browser as the following didn’t work. 192.168.0.1/collectd. I had to just the use IP of the Orange Pi like this ex. 192.168.0.1 and it loaded the graphs.
Hope this helps. Thanks jprochazka for the awesome work and support.
@jprochazka:
I have been trying to install dump1090 & rrdtools/collectd graphs on Orange Pi using your script.
With “Ubuntu_Vivid_Mate”, it succeede.
A large number of my attempts with two versions of Debian (“Jessie_Xfce” & “Jessie_Mini”) have failed till yesterday.
Last night I tried it again on Jessie_mini, and it is working ok now. New Year’s gift? .
Will try your script again on Jessie_Xfce shortly.
@mgunther:
I tried your method to manually install dump1090-mutability v1.15~dev on Orange PI.
It went ok with “Raspbian_For_OrangePi” and “Ubuntu_Vivid_Mate”.
With “Jessi_Xfce” and “Jessie_Mini”, it gives a broken .deb file.
Great, thanks sjacket99.
This isuue was giving me headaches, and made my microSD card cry (after each lost battle, I formatted the microSD card & made a fresh install of OS for the next attack).
@jprochazka:
CONGRATULATIONS & THANK YOU!
Couple of hours ago tried installation of dump1090-mutability & rrdtools/collected graphs on “Jessi_Xfce (Debian 8 )”, using your script, and it was successful. Seems your latest modifications made your scripts to cover Orange Pi OS also.
My priority was to solve installation problem related to dump1090 & graphs. To keep things simple, I did not install any data feeder. I am going to run the script again, this time choosing options for data feeders only. I will post the results after that.
Orange Pi PC Update Successful Manual Install of dump1090-mutability v1.15~dev, by upgrading mgunther’s method
I have faced multiple failed attempts to install dump1090-mutability v1.15~dev on Orange Pi/Debian_Jessi_Xfce and Debian_Jessie_Mini, using mgunther’s method.
I then carefully watched the output while jprochazka’s script was running on Debian Jessie Xfce. I noted several steps before actual package building steps. which showed that Orange Pi’s operating System software is much stripped down than Raspbian. Based on this observation, I added few steps before proceeding with mgunther’s manual install code for Raspbian. Thanks to sjacket99 who also provided useful tips. the additional commands I ran before mgunther’s method are:
I was able to Piaware 2.1-5 installed on the Orange Pi without issue. I first installed 2.1-3 Piaware then used my stat page to upgrade to 2.1-5. I don’t know if it will work for everyone put it did for me.
#Gave following command to enable connection of MLAT resuts
pi@OrangePI:~$ sudo piaware-config -mlatResultsFormat “beast,connect,localhost:30004”
pi@OrangePI:~$ sudo service piaware restart #alternate command: sudo /etc/init.d/piaware restart
#Again checked log, found all ok
pi@OrangePI:~$ cat /tmp/piaware.out #mlat(6633): Beast-format results connection with localhost:30004: connection established
949 msgs recv’d from dump1090-mutab (455 in last 5m); 949 msgs sent to FlightAware
mlat(6633): Receiver status: connected
mlat(6633): Server status: synchronized with 20 nearby receivers
mlat(6633): Receiver: 179.1 msg/s received 3.0kB/s from receiver
mlat(6633): Server: 1.1 kB/s from server 0.0kB/s TCP to server 1.8kB/s UDP to server
mlat(6633): Results: 499.0 positions/minute
mlat(6633): Aircraft: 33 of 44 Mode S, 6 of 8 ADS-B used
pi@OrangePI:~$
Orange PI PC install updates - Conclusion
I have been posting results of Manual Install (mgunther & Xforce)as well as Automated install by jprochazka’s script.
The purpose of Manual Install was to find a way out as initially jprochazka’s script, which were very successful with Raspberry Pi, were failing with Orange Pi. My latest install attempts during last two days have shown that now jprochazka’s script are debugged enough to give a successful install on Orange Pi PC with OS “Ubuntu_Vivid_Mate”, “Jessi_Mini”, and “Jessie_Xfce”. I continued manual install trials to find why manual install is failing with Jessie_Mini & Jessie_Xfce, while it succeeded with Ubuntu_Vivid_Mate. I finally found that the Orange Pi’s both Jessi distros lack many essential packages, which are required to be installed before manual install commands in mgunther’s method are run.
Since extra packages were installed before installation of dump1090-mutability v1.15~dev, as mentioned above, manual install of data feeders (piaware & planefinder) on Orange Pi PC were successful without any problems. Manual install of graphs (rrdtools/collectd) by Xforce’s web install script was also successful, but on some distros required changing in configuration file, the home directory from /var/www/html to /var/www. Also I have created a user “pi” and included it in “sudo” as a precaution, so that directory /home/pi with required folders/files is available for installation process which are sometimes hard-coded to /home/pi/
In view of ease and completeness of installation, I recommend use of jprochazka’s auto install script as first option, and use manual install as a fall-back in case someone ends up in issues with jprochazka’s auto install script.