wifi is disabled on the pi because it really sxcks it has full duplex link to my 3750 cisco switch
network is fine usb as well it is software iam 100% shore of it but i can not identify what .i did suspect the dump1090 application but after restarting this aplication only it did not go away i also change the rtl dongle for another one other brand ( although same chip set ) same problem
the funny thing is that it fixes it self without any intervening of me , again system is on 24/7
i put the pi in my network monitor tool ( observium ) and there is no evidence that something is wrong network wise
ps pi is not locking up its only that the output off dump1090 is not been tranferred somhow to the rest off the aplications
ps 2 using single core pi not overclocked and cpu load is 50 % so should be good
May not be related but my install has the pi and SDR Dongle located where the afternoon sun can get to it. (I know… improvements are planned).
The SDR Dongle is more heat sensitive than the pi. The pi runs fine at all times but I lose MLAT synchronization when the package gets too much sun. It then recovers by itself and the adventure repeats the next day.
PiAware 3.5.1 is now formally available. You may perform a package install/upgrade or install from the SD card image which is now available on our web site.
This release is a minor bug fix update which primarily addresses some bugs in Skyview. Please see the main post at the top of this thread for specific release notes.
One of my Pi’s is now on 3.5.3, but was not reporting any messages.
I logged into FA, brought up the Config screen and selected the “Reboot device” option.
I was rather surprised to see it run an update
I repeated the sequence on another Pi running 3.5.1 and it rebooted as expected (without updating)
Well. I have been observing a peculiar problem after updation to 3.5.3. I am using an orange,when it was 3.5.0 it was working well,even in 3.5.1 also but after updation to 3.5.3,it is showing an auto -disconnect tendency from the flight data but it stays connected with LAN and flightaware. I have to reboot it again to make it work. I already highlighted this problem to support but still no solution yet. I can’t blame my internet connection,it’s very stable as it was earlier. I tried a different router but this problem is still there. It’s dump 1090’s problem of getting self disconnected from flight and my whole skyview page going blank. No AJAX error either.
Did 3.5.3 break the logging to file?
I had a working 3.5.1 with logging to /var/log/piaware.log.
After manual update initiated from FA web site, there are no longer any log entries written.
Everything else seems to work normally.
01/18/2018 23:08:44 restarting piaware. hopefully i'll be right back...
01/18/2018 23:08:44 attempting to restart piaware using 'systemctl --no-block try-restart piaware.service < /dev/null'...
01/18/2018 23:08:44 piaware (process 407) is shutting down because it received a shutdown signal (SIGTERM) from the system...
01/18/2018 23:08:45 faup1090 exited with SIG SIGHUP
01/18/2018 23:08:45 multilateration data no longer required, disabling mlat client
01/18/2018 23:08:45 fa-mlat-client exited with SIG SIGTERM
01/18/2018 23:08:45 piaware (process 407) is exiting...
PiAware 3.x is designed for the most current Raspbian OS versions that uses systemd. I think there are a few features in piaware that will not work on the older OS.
The following command will output the OS version. Wheezy is the older OS version name. Jessie and Stretch are the new OS versions.
Sometimes upgrading breaks something, though this is rare. I had an upgrade from 3.5.1 to 3.5.3, and /var/log/piaware.log exists.
Output few minutes ago:
pi@piaware:~$ apt-cache policy piaware
piaware:
Installed: 3.5.3
Candidate: 3.5.3
Version table:
*** 3.5.3 0
500 http://flightaware.com/adsb/piaware/files/packages/ jessie/piaware armhf Packages
100 /var/lib/dpkg/status
pi@piaware:~$ cat /var/log/piaware.log
Jan 19 13:06:40 piaware piaware[470]: creating pidfile /run/piaware/piaware.pid
Jan 19 13:06:40 piaware piaware[470]: ****************************************************
Jan 19 13:06:40 piaware piaware[470]: piaware version 3.5.3 is running, process ID 470
Jan 19 13:06:40 piaware piaware[470]: your system info is: Linux piaware 4.4.50-v7+ #970 SMP Mon Feb 20 19:18:29 GMT 2017 armv7l GNU/Linux
.................
.................
.................
Jan 19 13:07:56 piaware piaware[470]: mlat-client(1066): Beast-format results connection with 127.0.0.1:30104: connection established
Jan 19 13:07:58 piaware piaware[470]: piaware has successfully sent several msgs to FlightAware!
Jan 19 13:12:15 piaware piaware[470]: 918 msgs recv'd from dump1090-fa (846 in last 5m); 721 msgs sent to FlightAware
@Skibox
As propsed by @david.baker, first check you OS by command cat /etc/os-release. If you have a Wheezy, better format your microSD card and write the latest Piaware image 3.5.3, which is Jessie based.
All our Pis are running Jessie, not the Piaware image but another Raspbian-based.
There will be no formatting of anything, all the units are remote and that s why it’s so important that updates are stable and reliable. They are also running much more important things than Piaware. Guess I just have to see at next reboot if that fixes the problem.