# Accessing PiAware Output File **URL:** \ **Category:** ADS-B Flight Tracking\ **Created:** [November 11, 2014, 5:21pm UTC](https://discussions.flightaware.com/t/accessing-piaware-output-file/15712 "2014-11-11T17:21:43Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![mwshell](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/mwshell/32/135884_2.png) [@mwshell](https://discussions.flightaware.com/u/mwshell)\ **Post date:** [November 11, 2014, 5:21pm UTC](https://discussions.flightaware.com/t/accessing-piaware-output-file/15712/1 "2014-11-11T17:21:43Z")
Hey All- Looks like my RPi hasnt checked in with FlightAware for the last couple hours and I’ve received an anomoly report again. I suspect it could be something on FlightAware’s side, because I have a friend who’s Pi hasn’t reported in the same timeframe mine has, and we live within 10 miles of each other. It seems odd that both our units would be behaving the exact same way. I rebooted my Pi and am hoping that will fix the issue, but I’d like to satisfy my curiousity and see if I can access the Pi’s output file on PiAware. However, I’m not quite sure how to access it. I know the code is ```auto /tmp/piaware.out ``` but when I enter that in the command line, I don’t get any output. Is there something I need to put in front of that? ---
**Author:** ![dbaker](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dbaker/32/97166_2.png) [@dbaker](https://discussions.flightaware.com/u/dbaker)\ **Post date:** [November 11, 2014, 5:35pm UTC](https://discussions.flightaware.com/t/accessing-piaware-output-file/15712/2 "2014-11-11T17:35:48Z")
```auto tail /tmp/piaware.out ``` or ```auto tail -f /tmp/piaware.out ``` …will update in real-time and hit control-c to end it. ---
**Author:** ![pault949](https://avatars.discourse-cdn.com/v4/letter/p/a587f6/32.png) [@pault949](https://discussions.flightaware.com/u/pault949)\ **Post date:** [November 11, 2014, 5:37pm UTC](https://discussions.flightaware.com/t/accessing-piaware-output-file/15712/3 "2014-11-11T17:37:36Z")
You need to use some type of text editor… ‘vi’ would work for sure, but it’s not easy to use unless you know how to use it… ‘cat’ would also work, but it dumps everything into the terminal window and you could miss some data if your terminal buffer isn’t on unlimited. Therefore, try ‘less’. That way you can read from the top all the way down and go back up in the file. Thanks, Paul ---
**Author:** ![IntenSiVuS](https://avatars.discourse-cdn.com/v4/letter/i/aca169/32.png) [@IntenSiVuS](https://discussions.flightaware.com/u/IntenSiVuS)\ **Post date:** [November 11, 2014, 5:45pm UTC](https://discussions.flightaware.com/t/accessing-piaware-output-file/15712/4 "2014-11-11T17:45:28Z")
same problem here,… piaware out is giving this output: 11/11/2014 17:39:57 connecting to FlightAware [eyes.flightaware.com/1200](http://eyes.flightaware.com/1200) 11/11/2014 17:40:03 FlightAware server SSL certificate validated 11/11/2014 17:40:03 encrypted session established with FlightAware 11/11/2014 17:40:56 3706 msgs recv’d from dump1090 via faup1090 (1829 in last 5m); 0 msgs sent to FlightAware 11/11/2014 17:40:57 connecting to FlightAware 70.42.6.203/1200 11/11/2014 17:41:01 FlightAware server SSL certificate validated 11/11/2014 17:41:01 encrypted session established with FlightAware 11/11/2014 17:41:57 connecting to FlightAware [eyes.flightaware.com/1200](http://eyes.flightaware.com/1200) 11/11/2014 17:42:03 FlightAware server SSL certificate validated 11/11/2014 17:42:03 encrypted session established with FlightAware 11/11/2014 17:42:57 connecting to FlightAware 70.42.6.203/1200 11/11/2014 17:42:58 got ‘couldn’t open socket: connection refused’ to adept server at 70.42.6.203/1200, will try again soon… and those last 2 lines keep repeating Something seems to be wrong at flightaware side ---
**Author:** ![mwshell](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/mwshell/32/135884_2.png) [@mwshell](https://discussions.flightaware.com/u/mwshell)\ **Post date:** [November 11, 2014, 5:56pm UTC](https://discussions.flightaware.com/t/accessing-piaware-output-file/15712/5 "2014-11-11T17:56:32Z")
> Something seems to be wrong at flightaware side I agree. At first, my unit was able to connect to FlighAware, but then I saw this: 11/11/2014 17:49:34 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good 11/11/2014 17:49:34 i see dump1090 serving on port 10001 11/11/2014 17:49:34 connecting to dump1090 on port 10001… 11/11/2014 17:49:34 piaware is connected to dump1090 on port 10001 11/11/2014 17:49:34 dump1090 is listening for connections on FA-style port 10001 11/11/2014 17:49:36 piaware received a message from the ADS-B source! 11/11/2014 17:50:04 12 msgs recv’d from dump1090; 0 msgs sent to FlightAware 11/11/2014 17:50:33 connecting to FlightAware 70.42.6.203/1200 11/11/2014 17:50:33 got ‘couldn’t open socket: connection refused’ to adept server at 70.42.6.203/1200, will try again soon… 11/11/2014 17:51:33 connecting to FlightAware [eyes.flightaware.com/1200](http://eyes.flightaware.com/1200) And it keeps repeating. ---
**Author:** ![dbaker](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dbaker/32/97166_2.png) [@dbaker](https://discussions.flightaware.com/u/dbaker)\ **Post date:** [November 11, 2014, 6:01pm UTC](https://discussions.flightaware.com/t/accessing-piaware-output-file/15712/6 "2014-11-11T18:01:57Z")
Server problems at the moment. ---
**Author:** ![dbaker](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dbaker/32/97166_2.png) [@dbaker](https://discussions.flightaware.com/u/dbaker)\ **Post date:** [November 11, 2014, 7:28pm UTC](https://discussions.flightaware.com/t/accessing-piaware-output-file/15712/7 "2014-11-11T19:28:47Z")
> [@dbaker](#): > > Server problems at the moment. PiAware service is back online – apologies for any confusion or wasted time. ---
**Author:** ![mwshell](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/mwshell/32/135884_2.png) [@mwshell](https://discussions.flightaware.com/u/mwshell)\ **Post date:** [November 11, 2014, 7:59pm UTC](https://discussions.flightaware.com/t/accessing-piaware-output-file/15712/8 "2014-11-11T19:59:07Z")
Things look good. Waiting for the anomoly to clear on the ADS-B page. 11/11/2014 19:53:25 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good 11/11/2014 19:53:25 i see dump1090 serving on port 10001 11/11/2014 19:53:25 connecting to dump1090 on port 10001… 11/11/2014 19:53:25 piaware is connected to dump1090 on port 10001 11/11/2014 19:53:25 dump1090 is listening for connections on FA-style port 10001 11/11/2014 19:53:25 piaware received a message from the ADS-B source! 11/11/2014 19:53:25 logged in to FlightAware as user mwshell 11/11/2014 19:53:56 7 msgs recv’d from dump1090; 6 msgs sent to FlightAware 11/11/2014 19:53:56 piaware has successfully sent several msgs to FlightAware! 11/11/2014 19:54:41 server is sending alive messages; we will expect them ---
**Author:** ![joelwiley](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/joelwiley/32/115128_2.png) [@joelwiley](https://discussions.flightaware.com/u/joelwiley)\ **Post date:** [February 11, 2015, 2:49am UTC](https://discussions.flightaware.com/t/accessing-piaware-output-file/15712/9 "2015-02-11T02:49:16Z")
❓