Since the issue with the gmail account being flagged and being corrected earlier this week I still see the empty log message when checking.
Surely I’ve logged in first and the logging is present in the commandline when being logged in to the Raspberry Pi.
Screenshot of the logs when logged in via the website
Screenshot of the status when logged in to the rapsberry Pi
Some questions:
Is this issue known?
Is it being worked on?
Is it something that is not running correctly on the serverside of FA or is there something the user can do (I can’t think of anything)?
The raspberry Pi is reporting normally, is shown being online and transmitting data so it looks like there might be a logging issue on the serverside?
Since I can look up the logs on the Pi itself it isn’t a big issue but I’m wondering if there are others that are seeing the same?
1 Like
Hi Tom,
Yes, exactly the same here.
Mine was like yours three days ago (right when that red bar issue on the screen started). It was normal yesterday and today, but tonight the problem you reported has started up again. My MLAT was also deactivated on two stations.
Hello, I had this issue around the same time, I struggled to get it to work, only after moving the USB to a different socket did it come on. However, just in the last 24 hours it has returned, did you folks get it resolved? is it a user end problem or flightaware. FA sent me the notification that they were no receiving any data. Any clues to get this resolved?
Cheers
Ashley
No I don’t have that issue at this moment.It’s a FA server side issue, not much you can do about that only checking if your processing is running correctly on the command line of the Pi itself
Sudo service dump1090-fa status
sudo service piaware status.
If one of them is failed you are not sending data.
thanks for your reply, i’m going to have do some research of getting back into rasberry pi, it has been years since i set it up initially and just some updating and switching it on and off to get it up and running again from time to time.
Hi All, sucessful update, thanks for your replies. As always it was a combination of events coming together that was obscuring the obvious. The raspberry Pi issue 4 b Pi aware was not connecting to the router. This I thougt was being masked by the fact that an updated router issued by EE seemed to haved messed with the ID names, Piaware had disappeared but a lot of netgear which I don’t own had appeared. Taking out and examining the SD card it was connected to an extender, which while showing all the correct lights was indeed not connecting to the router. I simply changed the settings to the main router (not quite as strong a signal as the extender) and all is up an running. For those thinking I must have changed the wifi settings on Piaware whent the new router arrived i avoided all that by setting the new router to the old name and password. I’ll have to try to remeber all this incase I get the error message again, although I have never seen that particular one before.
Thank you
Ashley
1 Like
