I recently upgraded my site from 7.2 to 8.2 The site is crashing every couple of hours now. I going to rebuild the SD card from scratch and see if I can get it stable. This is after an 82 day streak of uptime since I first installed this site on version 7.2
Has anyone else run into issues with 8.2? Any fixes out there. I can’t find anything in the log file that helps me.
Are you using the SD card image or a package add-on ?
What doe the logs tell you, is it restarting by itself of is it completly stopping ?
Yes I am using the SD Card Image.
Log before it just crashed.
[2023-01-30 13:21 UTC] 631964 msgs recv’d from dump1090-fa (990 in last 5m); 631964 msgs sent to FlightAware
[2023-01-30 13:26 UTC] 632899 msgs recv’d from dump1090-fa (935 in last 5m); 632899 msgs sent to FlightAware
[2023-01-30 13:31 UTC] 634029 msgs recv’d from dump1090-fa (1130 in last 5m); 634029 msgs sent to FlightAware
[2023-01-30 13:33 UTC] mlat-client(7135): Server status: synchronized with 479 nearby receivers
[2023-01-30 13:33 UTC] mlat-client(7135): Receiver: 250.0 msg/s received 100.4 msg/s processed (40%)
[2023-01-30 13:33 UTC] mlat-client(7135): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.3kB/s UDP to server
[2023-01-30 13:33 UTC] mlat-client(7135): Receiver status: connected
[2023-01-30 13:33 UTC] mlat-client(7135): Aircraft: 12 of 12 Mode S, 28 of 32 ADS-B used
[2023-01-30 13:36 UTC] 635111 msgs recv’d from dump1090-fa (1082 in last 5m); 635111 msgs sent to FlightAware
[2023-01-30 13:41 UTC] 636172 msgs recv’d from dump1090-fa (1061 in last 5m); 636172 msgs sent to FlightAware
[2023-01-30 13:46 UTC] 637059 msgs recv’d from dump1090-fa (887 in last 5m); 637059 msgs sent to FlightAware
[2023-01-30 13:48 UTC] mlat-client(7135): Receiver status: connected
[2023-01-30 13:48 UTC] mlat-client(7135): Aircraft: 3 of 4 Mode S, 26 of 28 ADS-B used
[2023-01-30 13:48 UTC] mlat-client(7135): Server status: synchronized with 483 nearby receivers
[2023-01-30 13:48 UTC] mlat-client(7135): Receiver: 212.3 msg/s received 90.2 msg/s processed (42%)
[2023-01-30 13:48 UTC] mlat-client(7135): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.1kB/s UDP to server
[2023-01-30 13:51 UTC] 637930 msgs recv’d from dump1090-fa (871 in last 5m); 637930 msgs sent to FlightAware
[2023-01-30 13:56 UTC] 638666 msgs recv’d from dump1090-fa (736 in last 5m); 638666 msgs sent to FlightAware
[2023-01-30 14:01 UTC] 639398 msgs recv’d from dump1090-fa (732 in last 5m); 639398 msgs sent to FlightAware
[2023-01-30 14:03 UTC] mlat-client(7135): Aircraft: 7 of 7 Mode S, 21 of 22 ADS-B used
[2023-01-30 14:03 UTC] mlat-client(7135): Server status: synchronized with 447 nearby receivers
[2023-01-30 14:03 UTC] mlat-client(7135): Receiver status: connected
[2023-01-30 14:03 UTC] mlat-client(7135): Results: 0.1 positions/minute
[2023-01-30 14:03 UTC] mlat-client(7135): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.0kB/s UDP to server
[2023-01-30 14:03 UTC] mlat-client(7135): Receiver: 195.7 msg/s received 76.1 msg/s processed (39%)
[2023-01-30 14:06 UTC] 640059 msgs recv’d from dump1090-fa (661 in last 5m); 640059 msgs sent to FlightAware
[2023-01-30 14:11 UTC] 640647 msgs recv’d from dump1090-fa (588 in last 5m); 640647 msgs sent to FlightAware
[2023-01-30 14:16 UTC] 641360 msgs recv’d from dump1090-fa (713 in last 5m); 641360 msgs sent to FlightAware
[2023-01-30 14:18 UTC] mlat-client(7135): Receiver status: connected
[2023-01-30 14:18 UTC] mlat-client(7135): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.0kB/s UDP to server
[2023-01-30 14:18 UTC] mlat-client(7135): Server status: synchronized with 512 nearby receivers
[2023-01-30 14:18 UTC] mlat-client(7135): Aircraft: 7 of 7 Mode S, 23 of 24 ADS-B used
[2023-01-30 14:18 UTC] mlat-client(7135): Receiver: 170.8 msg/s received 71.1 msg/s processed (42%)
[2023-01-30 14:18 UTC] mlat-client(7135): Results: 0.1 positions/minute
[2023-01-30 14:21 UTC] 642045 msgs recv’d from dump1090-fa (685 in last 5m); 642045 msgs sent to FlightAware
[2023-01-30 14:26 UTC] 642686 msgs recv’d from dump1090-fa (641 in last 5m); 642686 msgs sent to FlightAware
[2023-01-30 14:31 UTC] 643333 msgs recv’d from dump1090-fa (647 in last 5m); 643333 msgs sent to FlightAware
[2023-01-30 14:33 UTC] mlat-client(7135): Receiver status: connected
[2023-01-30 14:33 UTC] mlat-client(7135): Aircraft: 4 of 5 Mode S, 24 of 25 ADS-B used
[2023-01-30 14:33 UTC] mlat-client(7135): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.9kB/s UDP to server
[2023-01-30 14:33 UTC] mlat-client(7135): Results: 2.1 positions/minute
[2023-01-30 14:33 UTC] mlat-client(7135): Server status: synchronized with 464 nearby receivers
[2023-01-30 14:33 UTC] mlat-client(7135): Receiver: 172.6 msg/s received 68.3 msg/s processed (40%)
[2023-01-30 14:36 UTC] 644091 msgs recv’d from dump1090-fa (758 in last 5m); 644091 msgs sent to FlightAware
[2023-01-30 14:41 UTC] 644796 msgs recv’d from dump1090-fa (705 in last 5m); 644796 msgs sent to FlightAware
[2023-01-30 14:46 UTC] 645574 msgs recv’d from dump1090-fa (778 in last 5m); 645574 msgs sent to FlightAware
[2023-01-30 14:48 UTC] mlat-client(7135): Results: 2.1 positions/minute
[2023-01-30 14:48 UTC] mlat-client(7135): Aircraft: 6 of 8 Mode S, 24 of 29 ADS-B used
[2023-01-30 14:48 UTC] mlat-client(7135): Receiver: 197.2 msg/s received 75.6 msg/s processed (38%)
[2023-01-30 14:48 UTC] mlat-client(7135): Receiver status: connected
[2023-01-30 14:48 UTC] mlat-client(7135): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.0kB/s UDP to server
[2023-01-30 14:48 UTC] mlat-client(7135): Server status: synchronized with 485 nearby receivers
[2023-01-30 14:51 UTC] 646491 msgs recv’d from dump1090-fa (917 in last 5m); 646491 msgs sent to FlightAware
[2023-01-30 14:56 UTC] 647534 msgs recv’d from dump1090-fa (1043 in last 5m); 647534 msgs sent to FlightAware
[2023-01-30 15:01 UTC] 648708 msgs recv’d from dump1090-fa (1174 in last 5m); 648708 msgs sent to FlightAware
[2023-01-30 15:03 UTC] mlat-client(7135): Server status: synchronized with 515 nearby receivers
[2023-01-30 15:03 UTC] mlat-client(7135): Receiver: 277.1 msg/s received 105.8 msg/s processed (38%)
[2023-01-30 15:03 UTC] mlat-client(7135): Results: 3.8 positions/minute
[2023-01-30 15:03 UTC] mlat-client(7135): Aircraft: 3 of 4 Mode S, 36 of 39 ADS-B used
[2023-01-30 15:03 UTC] mlat-client(7135): Receiver status: connected
[2023-01-30 15:03 UTC] mlat-client(7135): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.3kB/s UDP to server
[2023-01-30 15:06 UTC] 649787 msgs recv’d from dump1090-fa (1079 in last 5m); 649787 msgs sent to FlightAware
[2023-01-30 15:11 UTC] 650900 msgs recv’d from dump1090-fa (1113 in last 5m); 650900 msgs sent to FlightAware
[2023-01-30 15:16 UTC] 651852 msgs recv’d from dump1090-fa (952 in last 5m); 651852 msgs sent to FlightAware
[2023-01-30 15:18 UTC] mlat-client(7135): Server status: synchronized with 456 nearby receivers
[2023-01-30 15:18 UTC] mlat-client(7135): Aircraft: 9 of 11 Mode S, 23 of 26 ADS-B used
[2023-01-30 15:18 UTC] mlat-client(7135): Receiver status: connected
[2023-01-30 15:18 UTC] mlat-client(7135): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.3kB/s UDP to server
[2023-01-30 15:18 UTC] mlat-client(7135): Receiver: 248.3 msg/s received 106.6 msg/s processed (43%)
[2023-01-30 15:21 UTC] 652764 msgs recv’d from dump1090-fa (912 in last 5m); 652764 msgs sent to FlightAware
[2023-01-30 15:26 UTC] 653707 msgs recv’d from dump1090-fa (943 in last 5m); 653707 msgs sent to FlightAware
[2023-01-30 15:31 UTC] 654795 msgs recv’d from dump1090-fa (1088 in last 5m); 654795 msgs sent to FlightAware
[2023-01-30 15:33 UTC] mlat-client(7135): Receiver status: connected
[2023-01-30 15:33 UTC] mlat-client(7135): Server status: synchronized with 492 nearby receivers
[2023-01-30 15:33 UTC] mlat-client(7135): Results: 2.0 positions/minute
[2023-01-30 15:33 UTC] mlat-client(7135): Receiver: 210.2 msg/s received 88.5 msg/s processed (42%)
[2023-01-30 15:33 UTC] mlat-client(7135): Aircraft: 5 of 8 Mode S, 25 of 28 ADS-B used
[2023-01-30 15:33 UTC] mlat-client(7135): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.1kB/s UDP to server
[2023-01-30 15:36 UTC] 655662 msgs recv’d from dump1090-fa (867 in last 5m); 655662 msgs sent to FlightAware
[2023-01-30 15:41 UTC] 656448 msgs recv’d from dump1090-fa (786 in last 5m); 656448 msgs sent to FlightAware
[2023-01-30 15:46 UTC] 657266 msgs recv’d from dump1090-fa (818 in last 5m); 657266 msgs sent to FlightAware
[2023-01-30 15:48 UTC] mlat-client(7135): Results: 8.9 positions/minute
[2023-01-30 15:48 UTC] mlat-client(7135): Aircraft: 6 of 8 Mode S, 24 of 25 ADS-B used
[2023-01-30 15:48 UTC] mlat-client(7135): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.1kB/s UDP to server
[2023-01-30 15:48 UTC] mlat-client(7135): Server status: synchronized with 498 nearby receivers
[2023-01-30 15:48 UTC] mlat-client(7135): Receiver: 210.0 msg/s received 86.3 msg/s processed (41%)
[2023-01-30 15:48 UTC] mlat-client(7135): Receiver status: connected
[2023-01-30 15:51 UTC] 658084 msgs recv’d from dump1090-fa (818 in last 5m); 658084 msgs sent to FlightAware
[2023-01-30 15:56 UTC] 658999 msgs recv’d from dump1090-fa (915 in last 5m); 658999 msgs sent to FlightAware
[2023-01-30 16:01 UTC] 660056 msgs recv’d from dump1090-fa (1057 in last 5m); 660056 msgs sent to FlightAware
[2023-01-30 16:03 UTC] mlat-client(7135): Receiver status: connected
[2023-01-30 16:03 UTC] mlat-client(7135): Results: 0.3 positions/minute
[2023-01-30 16:03 UTC] mlat-client(7135): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.1kB/s UDP to server
[2023-01-30 16:03 UTC] mlat-client(7135): Server status: synchronized with 515 nearby receivers
[2023-01-30 16:03 UTC] mlat-client(7135): Receiver: 199.4 msg/s received 82.5 msg/s processed (41%)
[2023-01-30 16:03 UTC] mlat-client(7135): Aircraft: 7 of 7 Mode S, 27 of 30 ADS-B used
[2023-01-30 16:06 UTC] 661081 msgs recv’d from dump1090-fa (1025 in last 5m); 661081 msgs sent to FlightAware
[2023-01-30 16:11 UTC] 662022 msgs recv’d from dump1090-fa (941 in last 5m); 662022 msgs sent to FlightAware
[2023-01-30 16:16 UTC] 662904 msgs recv’d from dump1090-fa (882 in last 5m); 662904 msgs sent to FlightAware
[2023-01-30 16:18 UTC] mlat-client(7135): Receiver status: connected
[2023-01-30 16:18 UTC] mlat-client(7135): Server status: synchronized with 504 nearby receivers
[2023-01-30 16:18 UTC] mlat-client(7135): Receiver: 231.5 msg/s received 93.6 msg/s processed (40%)
[2023-01-30 16:18 UTC] mlat-client(7135): Results: 0.2 positions/minute
[2023-01-30 16:18 UTC] mlat-client(7135): Aircraft: 5 of 6 Mode S, 29 of 32 ADS-B used
[2023-01-30 16:18 UTC] mlat-client(7135): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.2kB/s UDP to server
can you post the output of the following command ? that might give more insight since there are no things in the piaware log that seem to be wrong
sudo journalctl -eu dump1090-fa
I would be happy to except I have not learned yet how to access the console of my Raspberry 2 W yet. Can you recommend a way to access the Raspberry such as telnet or some thing like that. I do not have a display or keyboard attached.
Thanks in advance
It’s probably worth asking whether someone’s desktop computer is a Mac or Windows PC before you just throw PuTTY out as a solution. While Windows doesn’t support SSH natively from its command line, MacOS does, and doesn’t require additional software to be downloaded or installed.
The title of thread clearly specifies “Setup Putty in Windows”.
If user is not using Windows, he will simply ignore this guide.
I dont believe any user can be so dumb that even after reading “Windows” in the title as well as inside the guide, he will try to use the guide for Mac.
Curious, without console access to the Pi how did you upgrade from 7.2 to 8.2?
abcd567 sent instructions for console access via Windows, if you have Linux or Mac then just ignore the putty reference.
Geoff
Actually, since the April 2018 update to Windows 10, it does.
You are right that SSH can be done on Windows without PuTTY, but the guide I posted has two parts
(1) Enabling SSH on RPi
(2) installing PuTTY on Windows.
The item (2) can now be done throgh Windows terminal but item (1) is stll valid.
In addition to SSH, the PuTTY can perform many other functions as well, one of these shown in thread linked below. I dont know if Windows terminal can do these as well.
PuTTY is using the telnet protocol in that link.
Telnet has been a built-in component of Windows at least since Windows 3.1.1.
From that point through Windows XP, Telnet was enabled by default. Since it’s an insecure protocol, and will pass any provided credentials in clear text, it was disabled by default starting with Windows 7. It can easily be added back in (though not necessarily recommended) to Win7, Win8, Win10, and Win11 (and all comparable server versions since Server 2008) by using the “Add/Remove Components” tool in Windows. Note that there are separate options for enabling telnet client and telnet server. You would want the client option.
Once enabled, the “port exploring” described at the link could be accomplished by just opening a command prompt and typing
telnet <server name or IP> port
telnet 192.168.0.42 30003
This would stream any activity at that port to your console window (stdout). End the connection by hitting ctrl+c
If you wanted to save the output to a file, just add a greater-than symbol and a file name
telnet 192.168.0.42 30003 > PortOutput.txt
Or use a double greater-than to append the output to an existing file: (and create that file if it doesn’t exist)
telnet 192.168.0.42 30003 >> PortOutput.txt
Nice thing about not using PuTTY is that you don’t have to create a “connection”, and sift through a bunch of options that have a purpose but mostly aren’t required for simple things like this.
Interestingly, telnet was completely removed from MacOS some time ago, and can only be utilized by installing or compiling 3rd party software (there is even a port of PuTTY for Mac).
Thanks for the detailed information about telnet with Windows command prompt. Actually I have used it, but now forgot about it. If you scroll down to end of that thread, you will find my post in which I have shown how to use Windows command prompt to explore port 30003 using telnet.
Hmmm - I was going to post a note that I set the command to update to 8.2 and it’s not happening. I’m seeing a bunch of 404 messages. Can I assume the version I’m running is too old to upgrade using the online update option? Victor Engel ADS-B Feeder Statistics - FlightAware
Correct, we’ve ended support for Jessie OS. We recommend you follow this to upgrade and reclaim your existing site
OK. Thanks for the link. Looks like it will need to wait until the weekend, partly because the ladder I need to access the RPi is otherwise taken. I’ve had some recent unexpected outages that recovered after a few hours of doing nothing. Is that likely to be my RPi wearing out or an incompatibility of some sort causing issues?
Your PiAware powered off and back on a few hours ago, so power related issues is my guess (assuming you didn’t reboot it intentionally)
My internet was knocked out this morning during an online meeting I had. I didn’t notice a power cycle at the same time, but there might have been. I noticed another down time on the 16th for several hours. I tried rebooting by unplugging and replugging the extension cord, but that didn’t do anything. It’s possible there’s a loose power connection in the attic. I’ll take a look the next time I can get up there.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.