# No data-feed
**URL:** https://discussions.flightaware.com/t/no-data-feed/18143
**Category:** ADS-B Flight Tracking
**Created:** [March 11, 2016, 10:48pm UTC](https://discussions.flightaware.com/t/no-data-feed/18143 "2016-03-11T22:48:08Z")
**Posts on this page:** 17
**Page:** 1
### Author:  [@anon63922137](https://discussions.flightaware.com/u/anon63922137)
#### Post date: [March 11, 2016, 10:48pm UTC](https://discussions.flightaware.com/t/no-data-feed/18143/1 "2016-03-11T22:48:08Z")
Hi,
My receiver sends an hour ago no data and I do not know why.
Many receivers close to me have probably the same problem. Status Last seen: Today.
What can be wrong?
Greetings Marcus
---
### Author:  [@tjowen](https://discussions.flightaware.com/u/tjowen)
#### Post date: [March 11, 2016, 11:08pm UTC](https://discussions.flightaware.com/t/no-data-feed/18143/2 "2016-03-11T23:08:55Z")
see this thread…
[https://discussions.flightaware.com/ads-b-flight-tracking-f21/tls-alert-close-notify-keeps-happening-t36902.html](https://discussions.flightaware.com/t/tls-alert-close-notify-keeps-happening/18142)
no answers from the admin yet…
---
### Author:  [@JonHanford](https://discussions.flightaware.com/u/JonHanford)
#### Post date: [March 12, 2016, 12:09am UTC](https://discussions.flightaware.com/t/no-data-feed/18143/3 "2016-03-12T00:09:08Z")
It should be fixed now. Obj said there was a database hiccup that’s now resolved.
---
### Author:  [@keithroots](https://discussions.flightaware.com/u/keithroots)
#### Post date: [March 12, 2016, 7:29am UTC](https://discussions.flightaware.com/t/no-data-feed/18143/4 "2016-03-12T07:29:08Z")
Been off seven hours for me, shows FlightFeeder box as ‘live’ but no data feed. The box shows five ‘greens’ and the bytes sent is ticking up. I can see live data locally, but it’s obviously not getting to Flightaware.
---
### Author:  [@obj](https://discussions.flightaware.com/u/obj)
#### Post date: [March 12, 2016, 10:04am UTC](https://discussions.flightaware.com/t/no-data-feed/18143/5 "2016-03-12T10:04:07Z")
> [@keithroots](#):
>
> Been off seven hours for me, shows FlightFeeder box as ‘live’ but no data feed. The box shows five ‘greens’ and the bytes sent is ticking up. I can see live data locally, but it’s obviously not getting to Flightaware.
I see your FF was down from 2am - 8am UTC, but it seems to be back now. The timing suggests it is an unrelated problem as that was several hours after the piaware endpoint problem (plus current FFs use a different endpoint anyway)
---
### Author:  [@anon63922137](https://discussions.flightaware.com/u/anon63922137)
#### Post date: [March 12, 2016, 12:06pm UTC](https://discussions.flightaware.com/t/no-data-feed/18143/6 "2016-03-12T12:06:29Z")
Not working since 15 hours
“Anomaly report for PiAware feeder with a MAC address of…”
Other nearby receiver are working fine now.
VirtualRadarServer and other radar feeder are working too.
---
### Author:  [@keithroots](https://discussions.flightaware.com/u/keithroots)
#### Post date: [March 12, 2016, 1:48pm UTC](https://discussions.flightaware.com/t/no-data-feed/18143/7 "2016-03-12T13:48:47Z")
> [@obj](#):
>
> > [@keithroots](#):
> >
> > Been off seven hours for me, shows FlightFeeder box as ‘live’ but no data feed. The box shows five ‘greens’ and the bytes sent is ticking up. I can see live data locally, but it’s obviously not getting to Flightaware.
>
> I see your FF was down from 2am - 8am UTC, but it seems to be back now. The timing suggests it is an unrelated problem as that was several hours after the piaware endpoint problem (plus current FFs use a different endpoint anyway)
OK thanks, it’s all fine now, I did restart the box when I noticed the outage. Violent thunderstorms through the night were the probable cause.
---
### Author:  [@obj](https://discussions.flightaware.com/u/obj)
#### Post date: [March 12, 2016, 2:14pm UTC](https://discussions.flightaware.com/t/no-data-feed/18143/8 "2016-03-12T14:14:26Z")
> [@huebnermarcus](#):
>
> Not working since 15 hours
> “Anomaly report for PiAware feeder with a MAC address of…”
>
> Other nearby receiver are working fine now.
> VirtualRadarServer and other radar feeder are working too.
I don’t see any recent connection attempts from you; please check the piaware logs locally, it is probably unrelated to the DB problem.
---
### Author:  [@anon63922137](https://discussions.flightaware.com/u/anon63922137)
#### Post date: [March 12, 2016, 11:58pm UTC](https://discussions.flightaware.com/t/no-data-feed/18143/9 "2016-03-12T23:58:54Z")
> [@obj](#):
>
> > [@huebnermarcus](#):
> >
> > Not working since 15 hours
> > “Anomaly report for PiAware feeder with a MAC address of…”
> >
> > Other nearby receiver are working fine now.
> > VirtualRadarServer and other radar feeder are working too.
>
> I don’t see any recent connection attempts from you; please check the piaware logs locally, it is probably unrelated to the DB problem.
I think it’s working now.
My raspberry did not start properly.
Know it’s 1:00 am. No planes around Berlin.
We will see tomorrow. 🙂
But:
It took me seven hours to install dump and piaware again.
Your instructions did not work as it should.
Don’t know why.
EDIT:
1 hour later: dump is not running !!!
It’s frustrating…
---
### Author:  [@anon63922137](https://discussions.flightaware.com/u/anon63922137)
#### Post date: [March 13, 2016, 2:38pm UTC](https://discussions.flightaware.com/t/no-data-feed/18143/10 "2016-03-13T14:38:29Z")
New installation, no changes…
It works for 1 hour and then “no ADS-B data programm seen listening…”
---
### Author:  [@obj](https://discussions.flightaware.com/u/obj)
#### Post date: [March 13, 2016, 7:43pm UTC](https://discussions.flightaware.com/t/no-data-feed/18143/11 "2016-03-13T19:43:56Z")
dump1090 randomly crashing usually means a power or USB problem. Check “dmesg” output for USB problems.
---
### Author:  [@anon63922137](https://discussions.flightaware.com/u/anon63922137)
#### Post date: [March 14, 2016, 9:34am UTC](https://discussions.flightaware.com/t/no-data-feed/18143/12 "2016-03-14T09:34:46Z")
> [@obj](#):
>
> dump1090 randomly crashing usually means a power or USB problem. Check “dmesg” output for USB problems.
Another new installation.
It’s running now.
MAC address has changed.
Must this be changed? (Site Identifier)
---
### Author:  [@obj](https://discussions.flightaware.com/u/obj)
#### Post date: [March 14, 2016, 10:03am UTC](https://discussions.flightaware.com/t/no-data-feed/18143/13 "2016-03-14T10:03:06Z")
Your MAC address should not change unless you have changed hardware, assuming you are using a Raspberry Pi. If you’re not using a Pi, then you will need to diagnose the problem yourself, I can’t provide much help for other systems.
Regardless, I think you need to stop reinstalling and start explaining what you’re doing. If you reinstall every time there is a problem, you destroy any diagnostic information that could help fix the problem.
---
### Author:  [@anon63922137](https://discussions.flightaware.com/u/anon63922137)
#### Post date: [March 14, 2016, 10:53am UTC](https://discussions.flightaware.com/t/no-data-feed/18143/14 "2016-03-14T10:53:46Z")
> [@obj](#):
>
> Your MAC address should not change unless you have changed hardware, assuming you are using a Raspberry Pi. If you’re not using a Pi, then you will need to diagnose the problem yourself, I can’t provide much help for other systems.
> .
I’m using a Raspberry.
MAC Adress starts with 74:DA…
---
### Author:  [@FlightAwareSupport](https://discussions.flightaware.com/u/FlightAwareSupport)
#### Post date: [March 14, 2016, 11:03am UTC](https://discussions.flightaware.com/t/no-data-feed/18143/15 "2016-03-14T11:03:54Z")
FlightAware Support here.
Looking at your PiAware feed, for EDDT, you were online from 8th to 11th February and then offline until today.
The MAC address for this PiAware feed doesn’t begin “74:DA”. I may be looking at the wrong account?
You can view your statistics by selecting My ADS-B in your FlightAware account.
---
### Author:  [@obj](https://discussions.flightaware.com/u/obj)
#### Post date: [March 14, 2016, 11:06am UTC](https://discussions.flightaware.com/t/no-data-feed/18143/16 "2016-03-14T11:06:23Z")
> [@huebnermarcus](#):
>
> > [@obj](#):
> >
> > Your MAC address should not change unless you have changed hardware, assuming you are using a Raspberry Pi. If you’re not using a Pi, then you will need to diagnose the problem yourself, I can’t provide much help for other systems.
> > .
>
> I’m using a Raspberry.
> MAC Adress starts with 74:DA…
Raspberry Pi MAC addresses start with b8:27:eb and are found from the Pi’s CPU serial number which does not change.
You should be looking at the MAC address for eth0 even if you are using wireless; the wireless MAC address is not used.
---
### Author:  [@anon63922137](https://discussions.flightaware.com/u/anon63922137)
#### Post date: [March 14, 2016, 11:31am UTC](https://discussions.flightaware.com/t/no-data-feed/18143/17 "2016-03-14T11:31:40Z")
> [@obj](#):
>
> Raspberry Pi MAC addresses start with b8:27:eb and are found from the Pi’s CPU serial number which does not change.
> You should be looking at the MAC address for eth0 even if you are using wireless; the wireless MAC address is not used.
Ah, ok.
MAC from eth0 is correct.