Page 8 of 18 FirstFirst ... 678910 ... LastLast
Results 71 to 80 of 176

Thread: Problems with feeder statistics and data sharing

  1. #71
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,750
    Quote Originally Posted by Coxy View Post
    Might just be myset up.......wonder if my issue is due to using DVBT on the FR setup after the Dump1090 setup rather than running Beast????
    Most likely yes. If you already have dump1090-fa or dump1090-mutabity ver 1.15, and choose Receiver=DVBT, them fr24feed will install dump10o0-mutability v1.14, causing conflict between two versions of dump1090, and result in malfuntion.

  2. #72
    Flight attendant JohnnyBravo's Avatar
    Join Date
    Mar 2016
    Location
    T-EHGG148
    Posts
    53
    Quote Originally Posted by MarkDingo View Post
    This is a risky and short-term fix.

    Flightrader uses the Cloudflare CDN and for many reasons CDNs may move a service from one IP to another. Say if they are doing maintenance in one of their data centers. Cloudflare reasonably expects that they can make such changes by updating their DNS. In fact CDNs live and die by their ability to modify DNS answers in response to traffic loads and proximity data and whatnot.

    Not saying that your fix isn't useful, but it's something that needs to be periodically checked and removed as soon as practical.
    Perhaps a better solution to those who still want to run both IPv4 and IPv6 on their Pi's:

    In the file /etc/gai.conf find the following line:

    #precedence ::ffff:0:0/96 100

    Uncomment this line so it looks like:

    precedence ::ffff:0:0/96 100

    Your Pi will now prefer IPv4 over IPv6 without disabling IPv6.
    Both FR24 feeder and FlightAware feeder should now be happy and you don't have to worry about any DNS changes/updates.

    Hope this helps!

    Edit: If you have previously disabled IPv6 then you need to re-enable it for this to work properly!
    Last edited by JohnnyBravo; 2018-07-03 at 10:00.

  3. #73
    First officer
    Join Date
    Sep 2013
    Location
    Farnborough, UK
    Posts
    204
    Quote Originally Posted by ylis View Post
    Can you expand on this ? Clearly, some of us aren't hacker-savvy and don't know ...
    it wasn't about anything specific, just being sarcastic.
    T-EGLF8

  4. #74
    Purser
    Join Date
    Nov 2016
    Posts
    155
    Some significant changes to the data overnight in the Shared Stats ....

    ylis

  5. #75
    Passenger
    Join Date
    Jul 2018
    Location
    T-EGVF5/39/40
    Posts
    26
    Curiously monitoring dump1090 shows all my long range hits from North west, yet the polar plot indicates the only long range comes from the south east (where there is a ruddy great hill in the way? Also the 'range' indicates hits at 200nm+ yet the Maximum Distance seems less than half of that. (running a dedicated PI with an antenna above all local rooftops. Is it all still t1ts up?
    Last edited by mem0tap; 2018-07-06 at 08:29.

  6. #76
    Passenger
    Join Date
    Jan 2015
    Posts
    36
    Looks like stats have been fixed - up time has started to climb again and Max and Average ranges now correct, seemingly for everyone.

    T-EGSY1

  7. #77
    Passenger
    Join Date
    Jul 2018
    Location
    T-EGVF5/39/40
    Posts
    26
    Quote Originally Posted by Scroggie View Post
    Looks like stats have been fixed - up time has started to climb again and Max and Average ranges now correct, seemingly for everyone.

    T-EGSY1
    Lets just hope nobody lost their luggage!

    T-EGVF5

  8. #78
    Passenger
    Join Date
    Dec 2017
    Location
    T-EDDV13
    Posts
    15
    Well, I don't think, that maxrange and especially average range are showing correct data at this point. As the 30 days is used in the equation to calculate the average value and we have had an outage of several weeks, it will take 30 days to get the facts showing "correct" values again. Well, unless you add a floating equation, that increases the divider by one each day starting with with the number of days with data available. I won't expect FR24 to put in that amount of effort. So along with the uptime especially the avarage range should start to increase too.

    T-EDDV13

  9. #79
    Passenger
    Join Date
    May 2017
    Posts
    6
    Agreed. When the max range changed for first time in weeks I looked at the distances of a number of feeders, it was their current day max distance. It now appears to be the max distance is for the best day for each individual. And it appears to be what they were doing long before the database crash where your max distance was simply your best max in the past 30 days, and after 30 days it would drop to your next best.

  10. #80
    Passenger
    Join Date
    Jan 2015
    Posts
    36
    Yes agreed. I didn't mean "correct" in the literal sense just that the database was at last updating properly.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •