Version 2.3.0 Merged to master and New Image Released
Getting clean and ready to advance.
The main focus of this release was cleanup. Nearly every bit of bash scripting has been cleaned up, optimized, rewritten, or split apart. All descriptions, instructions, and user input in now displayed or collected via whiptail dialogs. Also the output generated by the scripts should be much more easier to view and read through.
The web portal’s advanced feature set has been worked on as well with the focus put on squashing any remaining bugs before work begins once again on adding new features. Speaking of advanced features the Python script collecting flight data has been optimized even more to cut back even further on system overhead.
There have been other bugs fixed since the v2.2.0 release as well. A full list of changes can be found below but first…
A Special thanks goes out to the following contributors!
@adamkaplan for his continued optimization of the flight logging script. @jdwall who contributed a new more graphical README as well as grammatical fixes.
Version 2.3.0 contains the following changes.
Massive clean up and in some cases an overhaul of the installation bash scripts.
Updated the dump978 map by modifying newer dump1090-mutability map.
Crontab errors pertaining to collectd no longer emailed to the root user.
The image setup script now executes the portal install scripts to setup the portal.
Script now comments out NET_BIND_ADDRESS to bind dump1090-mutability to all IPs.
Moved the logging portion of the portal install script into it’s own file. (advanced)
Flights.py has been optimized even further. (advanced)
Flights.py now logs the aircraft ID when logging positions. (advanced)
Many bug fixes pertainng to the advanced portal features setup process. (advanced)
Fix aircraft column issue not allowing SQLite installs to upgrade properly. (advanced)
Burned adsb-receiver_2.3.0_raspbian-jessie-lite.img
Ran ./install.sh twice.
dump1090-mutability, web portal/graphs, data feeders piaware, planefinder, flightradar24, and adsbexchange installed and configured.
By empty do you mean everything works but no data is displayed anywhere?
BTW you should be going to IP_ADDRESS/install.php to complete the installation.
I have been trying to get this working for months, everytime i do it the install page is blank, last week when i tried it would redirect to the piaware status page.
I need more information in order to help so if you could…
First off make quick edit to /etc/php5/cgi/php.ini…
sudo nano /etc/php5/cgi/php.ini
Look for…
display_errors = Off
Change this line to…
display_errors = On
Then reload Lighttpd…
sudo /etc/init.d/lighttpd force-reload
Then go to the blank page in question and report back any error you receive.
If you could pass along your browser and OS information as well that would be helpful also.
Whenever I go to the portal page I get automatically redirected to the /install/upgrade.php page. It also seems like my time zone isn’t saving. Any ideas as to what would be causing this? I’m at a loss.
It was after an upgrade. I’m pretty sure I don’t have the advanced portal features enabled. You think it would make sense to just start over with a clean install?
I just ran the upgrade again and now I’m in the same scenario as the other poster who said he gets nothing but a blank page, which is what I’m also getting now. The source for that page, according to Chrome, is this:
I used the script this morning per direction from ABCD567.
Worked FLAWLESSLY. I started from a brand new image of Raspbian, updated and set up for wifi. Nothing else.
I had to work hard to pick my jaw off the floor when it was over.
Two comments: 1) when my terminal window changed to the script terminal, the font was very light, I don’t know if that is configurable. 2) It would be helpful if early on you had a note that said for this to complete you need the following information so gather it up before you start. I had it all handy, but was worried something would go wrong or time out.
I rewrote the scripts to add a little more contrast between text explaining what is going on and what is actually going on. Might have missed switching to the default text color somewhere along the way. I will take a look into fixing this for the next release. Until then log out and back in and things should be back to normal.
If logging out is too much of a pain execute the following line:
echo -e "Changing font color to the \e[49mdefault color..."
I tried this image, but could not get it to work with wifi dongle. Edited the file called out at the WIKI. Are the drivers for the KanaKIT wifi USB in the image?