Getting a message when trying to connect to piaware.flightaware.com/1200 ‘couldn’t open socket, connection refused’ … This on a stable production piaware. Have verified general ip connectivity… Server side problems today?
Ok, rebooted the pi and got it to connect. Pi had dropped eth0 it appears. Hmm. Hardware Ethernet, rest of the lan is ops normal, odd.
So it is working now.
Possibly related, I have been getting “cpu utilization high” warnings. Says to run less stuff on the pi. What might I consider killing off? Not running anything other than the stock sd card distro configuration, so…
If it’s an original type Pi (not Pi2) then maybe MLAT might be worth disabling.
Yep, it is a Pi model B+ . Replacement Pi2 B ordered. Hopefully it will be a plug and play, swap the sd card over sort of thing.
Since it will be new hardware I believe your FA site number will change and past stats gone unless you spoof the MAC address to be the same as your old RPi.
Overclock the B+. It will help until you get the Pi2 (however, best not to overclock the pi2).
Thanks, I will do that. The “CPU load is high” advisory message seems to come and go, and does seem to correlate to the amount on MLAT traffic being processed. I do not want to turn off MLAT though!
Boy, I sure hope not. Spoofing the MAC is not something I know how to do, though I am sure I could figure it out with a little research. I am hoping that Flightaware can arrange a account “transfer” in support of the hardware upgrade, so I don’t lose my stats etc.
What’s the command to read out current CPU load? I used to know that a long time ago in a galaxy far, far away…
uptime
Spoofing the mac is really simple on the RPi
in /boot/cmdline.txt add this:
smsc95xx.macaddr=xx:xx:xx:xx:xx:xx
replacing with the mac address you want to use.
OK, you are officially awesome. Thank you!
I am also getting this on the site web page Log window – not all the time but fairly often. I wonder if this is related to the high CPU load issue as well?
Sorry, we were unable to fetch the log for this site. Please try again later