Release EDDN - Elite Dangerous Data Network. Trading tools sharing info in an unified way.

Status
Thread Closed: Not open for further replies.
What is this "54e7524c34593ad22c335793_ED Central Production Server_v0.2.3" that seems to be spamming old data - much of it without system a name?

Code:
@ LP 131-55/Abernathy Landing
      Animal Meat                1293       0       419L         -  2015-02-21 00:32:51  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Clothing                    317       0      1513L         -  2015-02-21 00:32:51  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Coffee                     1293       0       105L         -  2015-02-21 00:32:51  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Consumer Technology        6597       0       210L         -  2015-02-21 00:32:51  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Domestic Appliances         530       0       452L         -  2015-02-21 00:32:51  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Fish                        406       0      1171L         -  2015-02-21 00:32:51  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Food Cartridges             174       0        78L         -  2015-02-21 00:32:51  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Fruit And Vegetables        317       0       378L         -  2015-02-21 00:32:51  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Grain                       209       0      2524L         -  2015-02-21 00:32:51  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Hydrogen Fuel               107     111          ?    11479M  2015-02-21 00:32:51  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Mineral Oil                 194       0     42508L         -  2015-02-21 00:32:51  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Synthetic Meat              254       0       244L         -  2015-02-21 00:32:51  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Tea                        1467       0       380L         -  2015-02-21 00:32:51  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
@ /Abernathy Landing
      Aluminium                   234     251          ?     9772M  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Basic Medicines             356       0        76L         -  2015-02-21 00:33:02  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Bauxite                     153       0     19224L         -  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Beryllium                  7932    8018          ?      676M  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Cobalt                      577     601          ?     6274M  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Combat Stabilisers         2932       0          ?         -  2015-02-21 00:33:02  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Copper                      370     387          ?    68286M  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Gallium                    4920    4975          ?      969M  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Gold                       9238    9238          ?     1082M  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Indium                     5661    5723          ?     8770M  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Liquor                      768       0       277M         -  2015-02-21 00:33:02  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Lithium                    1405    1440          ?     2442M  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Microbial Furnaces          201       0     40392L         -  2015-02-21 00:33:02  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Mineral Extractors          593       0      3921L         -  2015-02-21 00:33:02  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Narcotics                   209       0         8L         -  2015-02-21 00:33:02  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Palladium                 13535   13536          ?       90L  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Performance Enhancers      6597       0          ?        7?  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Polymers                     63      76          ?    28698M  2015-02-21 00:33:02  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Power Generators            530       0      2833L         -  2015-02-21 00:33:02  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Progenitor Cells           6597       0       117L         -  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Semiconductors              763     783          ?     3885M  2015-02-21 00:33:02  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Silver                     4561    4612          ?     1353M  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Superconductors              68    6519          ?     7916M  2015-02-21 00:33:02  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Tantalum                   3717    3759          ?    11949M  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Titanium                    879     902          ?    35055M  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Tobacco                    4731       0       141L         -  2015-02-21 00:33:02  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Uranium                    2452    2481          ?     1617M  2015-02-21 00:33:14  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Water Purifiers             302       0       640L         -  2015-02-21 00:33:02  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
      Wine                        254       0      1954L         -  2015-02-21 00:33:02  # 54e7524c34593ad22c335793_ED Central Production Server_v0.2.3
 
Last edited:
Database store for EDDN

In an attempt to bridge the gap between where EDDN is now, and systems like trade dangerous, I've implemented my first go at storing and publishing data from EDDN. If it gets enough interest, I'll add more features. Let's see what response this gets.

You can get a trade dangerous-ish dump of my database from - It's real-time (IE, calling this URL reads the data from the database, not a pregenerated file). The database is updating from EDDN in real time.

This wonderful board won't let me post links, so change fix the URL as should be obvious:

http://eddndb.orcas.net/cgi-bin/tdexport.prices

Let me know what you think.
 
Last edited:
It ALSO means EDDN must mature (new Json format which has info for a complete station) and become redundant, scalable (we now have 20 Mbit unmethered and one Athlon CPU provided for free by a hosting provider. If not for them their might not have been an EDDN!!!).

I've got a quad core Xeon with a gigabit (actually 40 Gigabit, but the server's only got a gigabit connection) of internet bandwidth. Maybe I can help out here?
 
Last edited:
Could support for system traffic data be added?

I it would be nice if the tools like Trade Dangerous could modify routes/runs based on the amount and type of ship traffic.


If I am a trader and have hold full of something expensive it would be nice to plot a route through nearby stations with the least traffic in Vipers, Cobras or other ships that bad guys might use. You could also simply base the route on low overall traffic, the idea being I don't want to run into anybody if I can help it.

if EDDN supports this it might make it more likely that the EliteOCR folks would let you capture that data ..... then TD could injest it

Thanks
 
It ALSO means EDDN must mature (new Json format which has info for a complete station) and become redundant, scalable (we now have 20 Mbit unmethered and one Athlon CPU provided for free by a hosting provider. If not for them their might not have been an EDDN!!!).

Is the project actually ready to go multi-site?

I could spool up a VPS for you in my data center. We're located in the midwest, have generator backup and I'm in the process of installing a second provider into the facility for redundancy/diversity.

While my facility certainly isn't large, it's reliable and under my direct control - as opposed to a rented server somewhere.

If you're interested please PM me and we can discuss more details so that you can decide if it would be helpful for the project.
 
I wouldn't worry about its reliability, the current server is fully scalable, including increasing the bandwidth. It's current resources are simply all that was needed to start the project, but if it becomes a bottleneck we'll just have to revisit the allocation. As far as reliability and redundancy goes it currently has full backups, a UPS, a facility wide generator, and redundant connections.
 
Is anyone having trouble with the EDDN feed at the moment? I have been tracking some intermittant and sporadic relaying in the past 24hrs.

I have also been comparing lists of message source systems/stations. Is there an authoritative list of these? I only know of two feed trackers:
EDDN Feed: http://167.88.112.220
Maddavo: http://www.davek.com.au/td/

When I transmit in the usual way to EDDN the post seems to go through OK, but doesn't seem to come up on the trackers.
 

wolverine2710

Tutorial & Guide Writer
Is anyone having trouble with the EDDN feed at the moment? I have been tracking some intermittant and sporadic relaying in the past 24hrs.

I have also been comparing lists of message source systems/stations. Is there an authoritative list of these? I only know of two feed trackers:
EDDN Feed: http://167.88.112.220
Maddavo: http://www.davek.com.au/td/

When I transmit in the usual way to EDDN the post seems to go through OK, but doesn't seem to come up on the trackers.

I´ve send James a personal email about the situation. My fault, haven´t asked him what the correct procedure for stopping/starting the EDDN is. Will be corrected so that when there are problems at least two persons can restart the EDDN.
 
To me its little troubling that such service in which many people rely on is dependent on person who is not around for long periods of time. EDDN needs to be a service which is cared for on daily if not hourly basis in case of emergencies.
 
To me its little troubling that such service in which many people rely on is dependent on person who is not around for long periods of time. EDDN needs to be a service which is cared for on daily if not hourly basis in case of emergencies.

Offer me a salary, or accept a paid subscription model, and I'd gladly do so. But as a volunteer, I'm not going to and nor am I able to guarantee any SLA. And FWIW, I am "around" - when the forums bother to notify me of replies to the thread, I read them. I've not got time to actively develop new functionality for EDDN (though I still have items on the backlog for it, should I get the chance) but I'm more than willing to keep it ticking over.

- - - - - Additional Content Posted / Auto Merge - - - - -

Seems to be up again now.

Seems a transient problem, then, because I didn't actually do anything before you posted that!

I'll have a think about the best way to add a check for this scenario into the automated monitoring, because the relay and gateway both kept running happily throughout.
 
Offer me a salary, or accept a paid subscription model, and I'd gladly do so. But as a volunteer
There are many people who are active without being paid, this has nothing to with getting paid.

I am "around" - when the forums bother to notify me of replies to the thread, I read them.
Exactly my point, you are NOT around. Being around in the community is reading these forums regularly, like daily as many of us do.

I mean don't get me wrong you are free to do what ever you want, I'm not here to blame you. Just stating the obvious facts relating EDDN maintenance.
 
There are many people who are active without being paid, this has nothing to with getting paid.


Exactly my point, you are NOT around. Being around in the community is reading these forums regularly, like daily as many of us do.

Glass half empty much? Where is the -Rep button when you need it? Instead of bashing the guy that gives whatever free time he has, why don't you go bug FD about the API?
 
Offer me a salary, or accept a paid subscription model, and I'd gladly do so. But as a volunteer, I'm not going to and nor am I able to guarantee any SLA. And FWIW, I am "around" - when the forums bother to notify me of replies to the thread, I read them. I've not got time to actively develop new functionality for EDDN (though I still have items on the backlog for it, should I get the chance) but I'm more than willing to keep it ticking over.

dont let them get under your skin...not that you appeared to, just that I would have taken those comments with less restraint than I'd advise to others. I've seen similar comments on the thread for Slopey's tool, angry tirades about how bugs still weren't fixed after how many weeks??!? Guys, you aren't paying anyone's salary, so you can at least keep your comments civil. I mean, feel free of course to go write your own software. I wrote a small trade tracker for my own personal use. Sure, I could have angrily demanded better up-time or faster turn-around time on bugs from the existing projects, but that would have been silly, and the developers would have thought I was delusional. I'm not a silly delusional person, so I keep those comments "inside"
 
I think James has done excellent work and has donated a great deal of his time to this and he's due appreciation and patience, especially since this is still in alpha.

We're looking into possible solutions to improve the reliability and we'll post when we have some definite solutions figured out. Please be patient.
 

wolverine2710

Tutorial & Guide Writer
It looks things got a bit heated in the thread I created, in the process derailing it a bit. I'm not going to take sides. To me it looks as if it all boils to down to passion and caring. Posts on the Internet are not optimal, sometimes things are read/interpreted different then they are really meant. This goes for posts and their replies. We all care about EDDN and its future.

The facts as I see them. Wasn't if for this thread, the excellent work done by jamesremuscat (James revived the EMDN by Andreas) and Errantthought (the company he works for, Vivio Technologies, provided free hosting) there probably wouldn't be an EDDN to start with.

So a big thanks to those two commanders. The Alpha version of the EDDN is live now since the 15th of December. Approx 3.5 months. In that time aside from a few interrupts the EDDN has been stable as a rock. James said "I'll have a think about the best way to add a check for this scenario into the automated monitoring, because the relay and gateway both kept running happily throughout". That would solve the particular problem which did arise.

The current situation might not be ideal. Like I said I didn't ask James how to stop/start the EDDN, my bad. I now know how to do this. So now two commanders can stop/start the EDDN. James is GMT and I'm GMT+1. RL issues in combination with other projects prevents that EDDN is atm actively developed any further. I had plans to develop for the EDDN but I've RL issues and another project atm.

When the FD API arrives (haven't heart anything from it lately, last 5-6 weeks) and a LOT more data is coming to the EDDN things NEED to be changed. Like a JSON v2 to make to processing much more efficient (it now mimics Andreas EMDN format for backwards compatibility). Possibly there will be more dynamic data streams to take care of. I can think of a few more things.

Like its said before. The EDDN (like EMDN) is open source. Anyone can make a pull request for the EDDN, EDDN can be forked, even a completely dfferent EDDN can be created and hosted by a commander. More possiblities exist. I believe in software darwinism. The best suited program survives. So a lot of things can be done to improve the EDDN and or replace it. Perhaps there are commanders out there which DO have time.....
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom