Release EDDiscovery 19.X is out - ED Canonn Plugin is available, Python support, Latest data updates, new colonsation panel and engineering ship views

[D.D.Hariman]

We don't have any way of locking the ed launcher.. I've no idea what is going on with your pc. And the 3d map works for our users, we have not had any recent reports of problems

I have had this issue since the first time I tried to use EDD on my Dell 790. The solution sort of was to use the EDDPortable on a USB stick which worked but was painfully slow. It was suggested at that time to install a second internal HD and try the regular EDD installation to the second drive. I limped along on the USB and the 3D map that was was unusable.

I have upgraded to a Dell 990 with a second drive and I downloaded the normal EDD and installed it on the second drive. EDH launcher again refused to run. EDD worked great but without EDH it is useless.

Restored to before I installed EDD and then downloaded the EDDPortable to the second drive. Now both EDH and EDD work and the 3D map performs well except that I think I have my PC resolution set wrong for EDD to display properly.

In addition, as always, I get a security certificate error when I run EDD.

Screenshots are here. >>>> https://drive.google.com/open?id=0B3UfwiG4zNJfNjZHWkdCZ0l2RjQ

 

[Brian of Ardagh]

In addition, as always, I get a security certificate error when I run EDD.

Screenshots are here. >>>> https://drive.google.com/open?id=0B3UfwiG4zNJfNjZHWkdCZ0l2RjQ

That certificate error is a security warning that the application isn't signed. Assuming you know where you got the file from, you can uncheck the "Always ask when opening this file" and it shouldn't pop that warning up again.

I get the same thing with the EDD installer on Windows 10, it's not signed so I have to tell Windows it's okay to install.

 

[iain666]

Now both EDH and EDD work and the 3D map performs well except that I think I have my PC resolution set wrong for EDD to display properly.

We should be grand with whatever resolution you're using - you seem to have it set quite low looking at your screenshots but that's up to you to resize panels until you can see what you want to see. You can also adjust the font size by editing the theme in your settings.

I'd recommend 1920x1080 as a minimum resolution - but that's more a general having-a-PC-and-a-monitor-from-the-21st-century thing than an EDD thing.

 

[D.D.Hariman]

We should be grand with whatever resolution you're using - you seem to have it set quite low looking at your screenshots but that's up to you to resize panels until you can see what you want to see. You can also adjust the font size by editing the theme in your settings.

I'd recommend 1920x1080 as a minimum resolution - but that's more a general having-a-PC-and-a-monitor-from-the-21st-century thing than an EDD thing.

Well, The Dell 990 (quad i7 3.4GHz with a turbo mode to 3.8GHz) will soon get a ZOTAC GTX 1050 Ti. That will according to Game Debate put me well past EDH recommended.
The monitor at 17 inch diag is very likely my current limiting factor though it is a wide screen rather than square. The game is really ughly on square.
I have my eye on a couple 32" wide screens but they wouldn't really improve things without the 1050 TI so it comes first.

i will try the higher setting just to see what happens.

Thanks

Yep, Monitor is the limiting factor. 1440 X 900 is it's max.

 

[robbyp]

Signing the file is a significant amount of money (>$200 dollars) and a domain, and since EDD does not take donations at the point in time, we don't have a piggy bank to support buying this.

Most open source programs suffer from this hurdle.

 

[Eahlstan]

Since I've updated to the latest version (9.1.9) EDD sometimes seems to skip synchronisation with EGO and EDDN when it's idling in the background, about 50% of the systems I visited must be manually synced.
Is this an issue with the EGO/EDDN servers or is this EDD related?

Additionally I'm constantly getting 'Error sending EDSM events BadGateway', but there is no problem when syncing manually.

 

[Bravada Cadelanne]

Since I've updated to the latest version (9.1.9) EDD sometimes seems to skip synchronisation with EGO and EDDN when it's idling in the background, about 50% of the systems I visited must be manually synced.
Is this an issue with the EGO/EDDN servers or is this EDD related?

Additionally I'm constantly getting 'Error sending EDSM events BadGateway', but there is no problem when syncing manually.

EDSM has been giving 502 Bad Gateway errors sporadically due to heavy load.

Are there any errors in the trace log pertaining to the bodies / systems that are failing to sync?

 

[Eahlstan]

It's a bit strange:

Arrived at system Phraa Pruae IV-Y d7212 Visit No. 1
Arrived at system Phraa Pruae IV-Y d9119 Visit No. 1
Arrived at system Phraa Pruae IV-Y d6811 Visit No. 1
Arrived at system Phraa Pruae CA-A f1238 Visit No. 1
Arrived at system Phraa Pruae JV-Y d6601 Visit No. 1
Arrived at system Phraa Pruae JV-Y d6083 Visit No. 1
Arrived at system Phraa Pruae JV-Y d885 Visit No. 1
Checking for updated EDSM systems (may take a few moments).
Downloading systems from UTC 06.04.2018 17:59:20 to 06.04.2018 19:02:52
EDSM update complete with 1124 systems
Loading completed, total of 21 151 453 systems stored
Arrived at system Phraa Pruae JV-Y d1727 Visit No. 1
Arrived at system Phraa Pruae JV-Y d7927 Visit No. 1
Arrived at system Phraa Pruae JV-Y d4945 Visit No. 1
Arrived at system Phraa Pruae JV-Y d5251 Visit No. 1
Arrived at system Phraa Pruae JV-Y d2959 Visit No. 1
Arrived at system Phraa Pruae JV-Y d1394 Visit No. 1
Arrived at system Phraa Pruae JV-Y d1071 Visit No. 1
Adding FSDJump event to EDSM journal sync (Jump to Phraa Pruae JV-Y d1071)
Sent FSDJump event to EDDN (Jump to Phraa Pruae JV-Y d1071)
Adding Scan event to EDSM journal sync (Scan of Phraa Pruae JV-Y d1071 A)
Error sending EDSM events BadGateway
Sent Scan event to EDDN (Scan of Phraa Pruae JV-Y d1071 A)
Error sending EDSM events BadGateway
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d1071 A)
...
Sent Scan event to EGO (Scan of Phraa Pruae IV-Y d7212 B)
Sent Scan event to EGO (Scan of Phraa Pruae IV-Y d7212 C)
Sent Scan event to EGO (Scan of Phraa Pruae IV-Y d7212 D)
Sent Scan event to EDDN (Scan of Phraa Pruae IV-Y d7212 A)
Sent Scan event to EDDN (Scan of Phraa Pruae IV-Y d7212 B)
Sent Scan event to EDDN (Scan of Phraa Pruae IV-Y d7212 C)
Sent Scan event to EGO (Scan of Phraa Pruae IV-Y d9119 A)
Sent Scan event to EDDN (Scan of Phraa Pruae IV-Y d7212 D)
Sent Scan event to EDDN (Scan of Phraa Pruae IV-Y d9119 A)
Sent Scan event to EGO (Scan of Phraa Pruae IV-Y d9119 A 7)
Sent Scan event to EDDN (Scan of Phraa Pruae IV-Y d9119 A 7)
Sent Scan event to EDDN (Scan of Phraa Pruae IV-Y d6811)
Sent Scan event to EDDN (Scan of Phraa Pruae CA-A f1238)
Sent Scan event to EGO (Scan of Phraa Pruae IV-Y d6811)
Sent Scan event to EDDN (Scan of Phraa Pruae JV-Y d6601 A)
Sent Scan event to EDDN (Scan of Phraa Pruae JV-Y d6601 B)
Sent Scan event to EGO (Scan of Phraa Pruae CA-A f1238)
10 events in EGO queue
Sent Scan event to EDDN (Scan of Phraa Pruae JV-Y d6083)
Sent Scan event to EDDN (Scan of Phraa Pruae JV-Y d885 A)
Sent Scan event to EDDN (Scan of Phraa Pruae JV-Y d1727 A)
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d6601 A)
Sent Scan event to EDDN (Scan of Phraa Pruae JV-Y d7927 A)
Sent Scan event to EDDN (Scan of Phraa Pruae JV-Y d4945 A)
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d6601 B)
Sent Scan event to EDDN (Scan of Phraa Pruae JV-Y d5251 A)
Sent Scan event to EDDN (Scan of Phraa Pruae JV-Y d2959)
Sent Scan event to EDDN (Scan of Phraa Pruae JV-Y d1394 A)
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d6083)
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d885 A)
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d1727 A)
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d7927 A)
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d4945 A)
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d5251 A)
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d2959)
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d1394 A)


Seems like EDD ignores some of the log entries when they are first logged, but has no problem sending them manually.

 

[Bravada Cadelanne]

It's a bit strange:

Arrived at system Phraa Pruae IV-Y d7212 Visit No. 1
Arrived at system Phraa Pruae IV-Y d9119 Visit No. 1
Arrived at system Phraa Pruae IV-Y d6811 Visit No. 1
...
Arrived at system Phraa Pruae JV-Y d2959 Visit No. 1
Arrived at system Phraa Pruae JV-Y d1394 Visit No. 1
Arrived at system Phraa Pruae JV-Y d1071 Visit No. 1
Adding FSDJump event to EDSM journal sync (Jump to Phraa Pruae JV-Y d1071)
Sent FSDJump event to EDDN (Jump to Phraa Pruae JV-Y d1071)
Adding Scan event to EDSM journal sync (Scan of Phraa Pruae JV-Y d1071 A)
Error sending EDSM events BadGateway
Sent Scan event to EDDN (Scan of Phraa Pruae JV-Y d1071 A)
Error sending EDSM events BadGateway
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d1071 A)
...
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d5251 A)
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d2959)
Sent Scan event to EGO (Scan of Phraa Pruae JV-Y d1394 A)


Seems like EDD ignores some of the log entries when they are first logged, but has no problem sending them manually.

This looks like it's from the log window. It looks almost as if something is erroring out before EDSM and EDDB sync is complete.

What does the trace log in %LOCALAPPDATA%\EDDiscovery\Log\Trace_*.log contain pertaining to these entries.

 

[Eahlstan]

Sorry, I didn't know this log existed.

[2018-04-06 18:50:24Z] New entry 06.04.2018 18:50:30 FSDJump
[2018-04-06 18:50:25Z] Arrived at system: Phraa Pruae IV-Y d7212 1:th visit.
[2018-04-06 18:50:30Z] Exception NewPosition: Timeout für Vorgang überschritten
[2018-04-06 18:50:30Z] Trace: bei System.Net.HttpWebRequest.GetResponse()


[2018-04-06 18:50:30Z] bei BaseUtils.HttpCom.RequestGet(String action, NameValueCollection headers, Boolean handleException, Int32 timeout) in C:\Code\EDDiscovery\BaseUtils\HTTP\HttpCom.cs:Zeile 312.


[2018-04-06 18:50:30Z] bei EliteDangerousCore.EDSM.EDSMClass.GetJournalEventsToDiscard() in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMClass.cs:Zeile 839.


[2018-04-06 18:50:30Z] bei EliteDangerousCore.EDSM.EDSMJournalSync.SendEDSMEvents(Action`1 log, IEnumerable`1 helist, Boolean manual) in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMJournalSync.cs:Zeile 171.


[2018-04-06 18:50:30Z] bei EDDiscovery.EDDiscoveryForm.Controller_NewEntrySecond(HistoryEntry he, HistoryList hl) in C:\Code\EDDiscovery\EDDiscovery\EDDiscoveryForm.cs:Zeile 631.
[2018-04-06 18:50:30Z] New entry 06.04.2018 18:50:30 Music
[2018-04-06 18:50:31Z] New entry 06.04.2018 18:50:36 DiscoveryScan
[2018-04-06 18:50:32Z] Exception NewPosition: Der Remoteserver hat einen Fehler zurückgegeben: (502) Ungültiges Gateway.
[2018-04-06 18:50:32Z] Trace: bei System.Net.HttpWebRequest.GetResponse()


[2018-04-06 18:50:32Z] bei BaseUtils.HttpCom.RequestGet(String action, NameValueCollection headers, Boolean handleException, Int32 timeout) in C:\Code\EDDiscovery\BaseUtils\HTTP\HttpCom.cs:Zeile 312.


[2018-04-06 18:50:32Z] bei EliteDangerousCore.EDSM.EDSMClass.GetJournalEventsToDiscard() in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMClass.cs:Zeile 839.


[2018-04-06 18:50:32Z] bei EliteDangerousCore.EDSM.EDSMJournalSync.SendEDSMEvents(Action`1 log, IEnumerable`1 helist, Boolean manual) in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMJournalSync.cs:Zeile 171.


[2018-04-06 18:50:32Z] bei EDDiscovery.EDDiscoveryForm.Controller_NewEntrySecond(HistoryEntry he, HistoryList hl) in C:\Code\EDDiscovery\EDDiscovery\EDDiscoveryForm.cs:Zeile 631.
[2018-04-06 18:50:33Z] New entry 06.04.2018 18:50:39 DiscoveryScan
[2018-04-06 18:50:38Z] Exception NewPosition: Timeout für Vorgang überschritten
[2018-04-06 18:50:38Z] Trace: bei System.Net.HttpWebRequest.GetResponse()


[2018-04-06 18:50:38Z] bei BaseUtils.HttpCom.RequestGet(String action, NameValueCollection headers, Boolean handleException, Int32 timeout) in C:\Code\EDDiscovery\BaseUtils\HTTP\HttpCom.cs:Zeile 312.


[2018-04-06 18:50:38Z] bei EliteDangerousCore.EDSM.EDSMClass.GetJournalEventsToDiscard() in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMClass.cs:Zeile 839.


[2018-04-06 18:50:38Z] bei EliteDangerousCore.EDSM.EDSMJournalSync.SendEDSMEvents(Action`1 log, IEnumerable`1 helist, Boolean manual) in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMJournalSync.cs:Zeile 171.


[2018-04-06 18:50:38Z] bei EDDiscovery.EDDiscoveryForm.Controller_NewEntrySecond(HistoryEntry he, HistoryList hl) in C:\Code\EDDiscovery\EDDiscovery\EDDiscoveryForm.cs:Zeile 631.
[2018-04-06 18:50:47Z] New entry 06.04.2018 18:50:53 Scan
[2018-04-06 18:50:48Z] Exception NewPosition: Der Remoteserver hat einen Fehler zurückgegeben: (502) Ungültiges Gateway.
[2018-04-06 18:50:48Z] Trace: bei System.Net.HttpWebRequest.GetResponse()


[2018-04-06 18:50:48Z] bei BaseUtils.HttpCom.RequestGet(String action, NameValueCollection headers, Boolean handleException, Int32 timeout) in C:\Code\EDDiscovery\BaseUtils\HTTP\HttpCom.cs:Zeile 312.


[2018-04-06 18:50:48Z] bei EliteDangerousCore.EDSM.EDSMClass.GetJournalEventsToDiscard() in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMClass.cs:Zeile 839.


[2018-04-06 18:50:48Z] bei EliteDangerousCore.EDSM.EDSMJournalSync.SendEDSMEvents(Action`1 log, IEnumerable`1 helist, Boolean manual) in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMJournalSync.cs:Zeile 171.


[2018-04-06 18:50:48Z] bei EDDiscovery.EDDiscoveryForm.Controller_NewEntrySecond(HistoryEntry he, HistoryList hl) in C:\Code\EDDiscovery\EDDiscovery\EDDiscoveryForm.cs:Zeile 631.
[2018-04-06 18:50:54Z] New entry 06.04.2018 18:51:00 FuelScoop
[2018-04-06 18:50:58Z] New entry 06.04.2018 18:51:04 Music
[2018-04-06 18:50:59Z] Exception NewPosition: Der Remoteserver hat einen Fehler zurückgegeben: (502) Ungültiges Gateway.
[2018-04-06 18:50:59Z] Trace: bei System.Net.HttpWebRequest.GetResponse()


[2018-04-06 18:50:59Z] bei BaseUtils.HttpCom.RequestGet(String action, NameValueCollection headers, Boolean handleException, Int32 timeout) in C:\Code\EDDiscovery\BaseUtils\HTTP\HttpCom.cs:Zeile 312.


[2018-04-06 18:50:59Z] bei EliteDangerousCore.EDSM.EDSMClass.GetJournalEventsToDiscard() in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMClass.cs:Zeile 839.


[2018-04-06 18:50:59Z] bei EliteDangerousCore.EDSM.EDSMJournalSync.SendEDSMEvents(Action`1 log, IEnumerable`1 helist, Boolean manual) in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMJournalSync.cs:Zeile 171.


[2018-04-06 18:50:59Z] bei EDDiscovery.EDDiscoveryForm.Controller_NewEntrySecond(HistoryEntry he, HistoryList hl) in C:\Code\EDDiscovery\EDDiscovery\EDDiscoveryForm.cs:Zeile 631.
[2018-04-06 18:51:00Z] New entry 06.04.2018 18:51:06 FuelScoop
[2018-04-06 18:51:07Z] New entry 06.04.2018 18:51:12 Music
[2018-04-06 18:51:07Z] Exception NewPosition: Der Remoteserver hat einen Fehler zurückgegeben: (502) Ungültiges Gateway.
[2018-04-06 18:51:07Z] Trace: bei System.Net.HttpWebRequest.GetResponse()


[2018-04-06 18:51:07Z] bei BaseUtils.HttpCom.RequestGet(String action, NameValueCollection headers, Boolean handleException, Int32 timeout) in C:\Code\EDDiscovery\BaseUtils\HTTP\HttpCom.cs:Zeile 312.


[2018-04-06 18:51:07Z] bei EliteDangerousCore.EDSM.EDSMClass.GetJournalEventsToDiscard() in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMClass.cs:Zeile 839.


[2018-04-06 18:51:07Z] bei EliteDangerousCore.EDSM.EDSMJournalSync.SendEDSMEvents(Action`1 log, IEnumerable`1 helist, Boolean manual) in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMJournalSync.cs:Zeile 171.


[2018-04-06 18:51:07Z] bei EDDiscovery.EDDiscoveryForm.Controller_NewEntrySecond(HistoryEntry he, HistoryList hl) in C:\Code\EDDiscovery\EDDiscovery\EDDiscoveryForm.cs:Zeile 631.
[2018-04-06 18:51:09Z] New entry 06.04.2018 18:51:15 Scan
[2018-04-06 18:51:14Z] Exception NewPosition: Timeout für Vorgang überschritten
[2018-04-06 18:51:14Z] Trace: bei System.Net.HttpWebRequest.GetResponse()


[2018-04-06 18:51:14Z] bei BaseUtils.HttpCom.RequestGet(String action, NameValueCollection headers, Boolean handleException, Int32 timeout) in C:\Code\EDDiscovery\BaseUtils\HTTP\HttpCom.cs:Zeile 312.


[2018-04-06 18:51:14Z] bei EliteDangerousCore.EDSM.EDSMClass.GetJournalEventsToDiscard() in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMClass.cs:Zeile 839.


[2018-04-06 18:51:14Z] bei EliteDangerousCore.EDSM.EDSMJournalSync.SendEDSMEvents(Action`1 log, IEnumerable`1 helist, Boolean manual) in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMJournalSync.cs:Zeile 171.


[2018-04-06 18:51:14Z] bei EDDiscovery.EDDiscoveryForm.Controller_NewEntrySecond(HistoryEntry he, HistoryList hl) in C:\Code\EDDiscovery\EDDiscovery\EDDiscoveryForm.cs:Zeile 631.
[2018-04-06 18:51:20Z] New entry 06.04.2018 18:51:26 FuelScoop
[2018-04-06 18:51:30Z] New entry 06.04.2018 18:51:35 Scan
[2018-04-06 18:51:30Z] Exception NewPosition: Der Remoteserver hat einen Fehler zurückgegeben: (502) Ungültiges Gateway.
[2018-04-06 18:51:30Z] Trace: bei System.Net.HttpWebRequest.GetResponse()


[2018-04-06 18:51:30Z] bei BaseUtils.HttpCom.RequestGet(String action, NameValueCollection headers, Boolean handleException, Int32 timeout) in C:\Code\EDDiscovery\BaseUtils\HTTP\HttpCom.cs:Zeile 312.


[2018-04-06 18:51:30Z] bei EliteDangerousCore.EDSM.EDSMClass.GetJournalEventsToDiscard() in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMClass.cs:Zeile 839.


[2018-04-06 18:51:30Z] bei EliteDangerousCore.EDSM.EDSMJournalSync.SendEDSMEvents(Action`1 log, IEnumerable`1 helist, Boolean manual) in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMJournalSync.cs:Zeile 171.


[2018-04-06 18:51:30Z] bei EDDiscovery.EDDiscoveryForm.Controller_NewEntrySecond(HistoryEntry he, HistoryList hl) in C:\Code\EDDiscovery\EDDiscovery\EDDiscoveryForm.cs:Zeile 631.
[2018-04-06 18:51:36Z] Exception NewPosition: Timeout für Vorgang überschritten
[2018-04-06 18:51:36Z] Trace: bei System.Net.HttpWebRequest.GetResponse()


[2018-04-06 18:51:36Z] bei BaseUtils.HttpCom.RequestGet(String action, NameValueCollection headers, Boolean handleException, Int32 timeout) in C:\Code\EDDiscovery\BaseUtils\HTTP\HttpCom.cs:Zeile 312.


[2018-04-06 18:51:36Z] bei EliteDangerousCore.EDSM.EDSMClass.GetJournalEventsToDiscard() in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMClass.cs:Zeile 839.


[2018-04-06 18:51:36Z] bei EliteDangerousCore.EDSM.EDSMJournalSync.SendEDSMEvents(Action`1 log, IEnumerable`1 helist, Boolean manual) in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMJournalSync.cs:Zeile 171.


[2018-04-06 18:51:36Z] bei EDDiscovery.EDDiscoveryForm.Controller_NewEntrySecond(HistoryEntry he, HistoryList hl) in C:\Code\EDDiscovery\EDDiscovery\EDDiscoveryForm.cs:Zeile 631.
[2018-04-06 18:52:07Z] bei System.Net.HttpWebRequest.GetResponse()


[2018-04-06 18:52:07Z] bei BaseUtils.HttpCom.RequestGet(String action, NameValueCollection headers, Boolean handleException, Int32 timeout) in C:\Code\EDDiscovery\BaseUtils\HTTP\HttpCom.cs:Zeile 260.
[2018-04-06 18:52:07Z] WebException : Der Remoteserver hat einen Fehler zurückgegeben: (502) Ungültiges Gateway.
[2018-04-06 18:52:07Z] Response code : BadGateway
[2018-04-06 18:52:07Z] Response body : <html>


[2018-04-06 18:52:07Z] <head><title>502 Bad Gateway</title></head>


[2018-04-06 18:52:07Z] <body bgcolor="white">


[2018-04-06 18:52:07Z] <center><h1>502 Bad Gateway</h1></center>


[2018-04-06 18:52:07Z] <hr><center>nginx</center>


[2018-04-06 18:52:07Z] </body>


[2018-04-06 18:52:07Z] </html>


[2018-04-06 18:52:07Z]
[2018-04-06 18:52:07Z] Bad start and/or end times returned by EDSM - backing off for 660s
[2018-04-06 18:52:08Z] bei System.Net.HttpWebRequest.GetResponse()


[2018-04-06 18:52:08Z] bei BaseUtils.HttpCom.RequestGet(String action, NameValueCollection headers, Boolean handleException, Int32 timeout) in C:\Code\EDDiscovery\BaseUtils\HTTP\HttpCom.cs:Zeile 260.
[2018-04-06 18:52:13Z] New entry 06.04.2018 18:52:18 Scan
[2018-04-06 18:52:18Z] Exception NewPosition: Timeout für Vorgang überschritten
[2018-04-06 18:52:18Z] Trace: bei System.Net.HttpWebRequest.GetResponse()


[2018-04-06 18:52:18Z] bei BaseUtils.HttpCom.RequestGet(String action, NameValueCollection headers, Boolean handleException, Int32 timeout) in C:\Code\EDDiscovery\BaseUtils\HTTP\HttpCom.cs:Zeile 312.


[2018-04-06 18:52:18Z] bei EliteDangerousCore.EDSM.EDSMClass.GetJournalEventsToDiscard() in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMClass.cs:Zeile 839.


[2018-04-06 18:52:18Z] bei EliteDangerousCore.EDSM.EDSMJournalSync.SendEDSMEvents(Action`1 log, IEnumerable`1 helist, Boolean manual) in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMJournalSync.cs:Zeile 171.


[2018-04-06 18:52:18Z] bei EDDiscovery.EDDiscoveryForm.Controller_NewEntrySecond(HistoryEntry he, HistoryList hl) in C:\Code\EDDiscovery\EDDiscovery\EDDiscoveryForm.cs:Zeile 631.
[2018-04-06 18:52:29Z] New entry 06.04.2018 18:52:34 StartJump
[2018-04-06 18:52:29Z] Exception NewPosition: Der Remoteserver hat einen Fehler zurückgegeben: (502) Ungültiges Gateway.
[2018-04-06 18:52:29Z] Trace: bei System.Net.HttpWebRequest.GetResponse()


[2018-04-06 18:52:29Z] bei BaseUtils.HttpCom.RequestGet(String action, NameValueCollection headers, Boolean handleException, Int32 timeout) in C:\Code\EDDiscovery\BaseUtils\HTTP\HttpCom.cs:Zeile 312.


[2018-04-06 18:52:29Z] bei EliteDangerousCore.EDSM.EDSMClass.GetJournalEventsToDiscard() in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMClass.cs:Zeile 839.


[2018-04-06 18:52:29Z] bei EliteDangerousCore.EDSM.EDSMJournalSync.SendEDSMEvents(Action`1 log, IEnumerable`1 helist, Boolean manual) in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMJournalSync.cs:Zeile 171.


[2018-04-06 18:52:29Z] bei EDDiscovery.EDDiscoveryForm.Controller_NewEntrySecond(HistoryEntry he, HistoryList hl) in C:\Code\EDDiscovery\EDDiscovery\EDDiscoveryForm.cs:Zeile 631.

//next jump

[2018-04-06 20:51:03Z] Adding FSDJump event to EDSM journal sync (Jump to Phraa Pruae IV-Y d7212)
[2018-04-06 20:51:03Z] Adding Scan event to EDSM journal sync (Scan of Phraa Pruae IV-Y d7212 A)
[2018-04-06 20:51:03Z] Adding Scan event to EDSM journal sync (Scan of Phraa Pruae IV-Y d7212 B)
[2018-04-06 20:51:03Z] Adding Scan event to EDSM journal sync (Scan of Phraa Pruae IV-Y d7212 C)
[2018-04-06 20:51:03Z] Adding Scan event to EDSM journal sync (Scan of Phraa Pruae IV-Y d7212 D)

//more stuff

[2018-04-06 20:51:06Z] Error submitting event 243841 "Scan of Phraa Pruae IV-Y d7212 A": 402 Item unknown
[2018-04-06 20:51:06Z] Error submitting event 243846 "Scan of Phraa Pruae IV-Y d7212 B": 402 Item unknown
[2018-04-06 20:51:06Z] Error submitting event 243848 "Scan of Phraa Pruae IV-Y d7212 C": 402 Item unknown
[2018-04-06 20:51:06Z] Error submitting event 243849 "Scan of Phraa Pruae IV-Y d7212 D": 402 Item unknown

//some more stuff

[2018-04-06 23:20:31Z] Adding Scan event to EDSM journal sync (Scan of Phraa Pruae IV-Y d7212 A)
[2018-04-06 23:20:31Z] Adding Scan event to EDSM journal sync (Scan of Phraa Pruae IV-Y d7212 B)
[2018-04-06 23:20:31Z] Adding Scan event to EDSM journal sync (Scan of Phraa Pruae IV-Y d7212 C)
[2018-04-06 23:20:31Z] Adding Scan event to EDSM journal sync (Scan of Phraa Pruae IV-Y d7212 D)





There is no folder named 'C:\code\' on my system.


Right at the new start today it logged:

[2018-04-07 13:30:49Z] Running logfile age check
[2018-04-07 13:30:49Z] Native library pre-loader is trying to load native SQLite library "D:\EDDiscovery\x64\SQLite.Interop.dll"...
[2018-04-07 13:30:49Z] SQLite version 3.21.0
[2018-04-07 13:30:50Z] *** Elite Dangerous Discovery Initializing - Version 9.1.9.0 (Using D:\EDDiscovery\), Platform: Win32NT
[2018-04-07 13:30:50Z] Theme ID 10037
[2018-04-07 13:30:52Z] New watch on C:\Users\Eahlstan\Saved Games\Frontier Developments\Elite Dangerous
[2018-04-07 13:30:52Z] Scanned C:\Users\Eahlstan\Saved Games\Frontier Developments\Elite Dangerous
[2018-04-07 13:31:03Z] Failed to add body Eol Prou MR-V d2-640 A 1 to system - too deep
[2018-04-07 13:31:03Z] Failed to add body Eol Prou MR-V d2-640 A 2 to system - too deep
//much more too deep stuff
[2018-04-07 13:31:50Z] Thread Star Distance Worker waiting for thread Background Worker Thread to finish writer
[2018-04-07 13:31:50Z] The transaction lock has been held for a long time.
[2018-04-07 13:31:50Z] Thread waiting for thread Background Worker Thread to finish writer
[2018-04-07 13:31:55Z] Start Monitor on C:\Users\Eahlstan\Saved Games\Frontier Developments\Elite Dangerous
[2018-04-07 13:31:55Z] EDSM Fetch logs start with cmdr 1
[2018-04-07 13:31:55Z] EDSM Fetch logs restart time
[2018-04-07 13:31:55Z] EDSM Thread logs start
[2018-04-07 13:31:56Z] Thread Background Worker Thread waiting for readers to finish
[2018-04-07 13:31:57Z] Thread Star Distance Worker waiting for thread Background Worker Thread to finish writer
[2018-04-07 13:31:57Z] Last message repeated 5 times
[2018-04-07 13:31:57Z] The transaction lock has been held for a long time.
[2018-04-07 13:31:57Z] Last message repeated 11 times
[2018-04-07 13:31:57Z] Thread waiting for thread Background Worker Thread to finish writer
[2018-04-07 13:31:57Z] Last message repeated 5 times
[2018-04-07 13:31:57Z] Thread Background Worker Thread waiting for readers to finish
[2018-04-07 13:31:58Z] EDSM Comments downloaded/updated 0
[2018-04-07 13:31:59Z] Thread Background Worker Thread waiting for readers to finish
[2018-04-07 13:31:59Z] Thread Background Worker Thread waiting for readers to finish
[2018-04-07 13:32:44Z] Database locked - retrying
[2018-04-07 13:32:44Z] bei System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)


[2018-04-07 13:32:44Z] bei System.Data.SQLite.SQLiteDataReader.NextResult()


[2018-04-07 13:32:44Z] bei System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)


[2018-04-07 13:32:44Z] bei System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)


[2018-04-07 13:32:44Z] bei EliteDangerousCore.DB.SQLiteDataReaderED`1..ctor(DbCommand cmd, CommandBehavior behaviour, SQLiteTransactionED`1 txn, SQLiteTxnLockED`1 txnlock) in C:\Code\EDDiscovery\EliteDangerous\DB\SQLiteCommandED.cs:Zeile 339.


[2018-04-07 13:32:44Z] bei EliteDangerousCore.DB.SQLiteCommandED`1.ExecuteDbDataReader(CommandBehavior behavior) in C:\Code\EDDiscovery\EliteDangerous\DB\SQLiteCommandED.cs:Zeile 490.
[2018-04-07 13:32:45Z] Thread Background Worker Thread waiting for readers to finish
[2018-04-07 13:32:45Z] Last message repeated 9 times

//reruns of 'Database locked'

[2018-04-07 13:45:58Z] Failed to add body Eol Prou MR-V d2-640 A 1 to system - too deep
[2018-04-07 13:45:58Z] Failed to add body Eol Prou MR-V d2-640 A 2 to system - too deep
[2018-04-07 13:45:58Z] Failed to add body Eol Prou IK-D b14-60 AB 2 to system - too deep
...


[2018-04-07 13:45:58Z] Failed to add body Phaa Chruia XV-E d11-1293 B 3 to system - too deep
[2018-04-07 13:47:12Z] Start Monitor on C:\Users\Eahlstan\Saved Games\Frontier Developments\Elite Dangerous
[2018-04-07 13:47:12Z] EDSM Fetch logs start with cmdr 1
[2018-04-07 13:47:12Z] EDSM Thread logs start
[2018-04-07 13:47:14Z] EDSM Comments downloaded/updated 0

No more entries since then - I haven't started the game yet.

I start EDD with:

Appfolder D:\EDDiscovery\
Userdbpath D:\EDDiscovery\EDDUser.sqlite
Systemsdbpath D:\EDDiscovery\EDDSystem.sqlite

 

[Bravada Cadelanne]

Sorry, I didn't know this log existed.

[2018-04-06 18:50:24Z] New entry 06.04.2018 18:50:30 FSDJump
[2018-04-06 18:50:25Z] Arrived at system: Phraa Pruae IV-Y d7212 1:th visit.
[2018-04-06 18:50:30Z] Exception NewPosition: Timeout für Vorgang überschritten
[2018-04-06 18:50:30Z] Trace: bei System.Net.HttpWebRequest.GetResponse()
[2018-04-06 18:50:30Z] bei BaseUtils.HttpCom.RequestGet(String action, NameValueCollection headers, Boolean handleException, Int32 timeout) in C:\Code\EDDiscovery\BaseUtils\HTTP\HttpCom.cs:Zeile 312.
[2018-04-06 18:50:30Z] bei EliteDangerousCore.EDSM.EDSMClass.GetJournalEventsToDiscard() in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMClass.cs:Zeile 839.
[2018-04-06 18:50:30Z] bei EliteDangerousCore.EDSM.EDSMJournalSync.SendEDSMEvents(Action`1 log, IEnumerable`1 helist, Boolean manual) in C:\Code\EDDiscovery\EliteDangerous\EDSM\EDSMJournalSync.cs:Zeile 171.
[2018-04-06 18:50:30Z] bei EDDiscovery.EDDiscoveryForm.Controller_NewEntrySecond(HistoryEntry he, HistoryList hl) in C:\Code\EDDiscovery\EDDiscovery\EDDiscoveryForm.cs:Zeile 631.

This looks like the cause was the same as the 502 Bad Gateway errors that you saw logged.

//next jump

[2018-04-06 20:51:03Z] Adding FSDJump event to EDSM journal sync (Jump to Phraa Pruae IV-Y d7212)
[2018-04-06 20:51:03Z] Adding Scan event to EDSM journal sync (Scan of Phraa Pruae IV-Y d7212 A)
[2018-04-06 20:51:03Z] Adding Scan event to EDSM journal sync (Scan of Phraa Pruae IV-Y d7212 B)
[2018-04-06 20:51:03Z] Adding Scan event to EDSM journal sync (Scan of Phraa Pruae IV-Y d7212 C)
[2018-04-06 20:51:03Z] Adding Scan event to EDSM journal sync (Scan of Phraa Pruae IV-Y d7212 D)

//more stuff

[2018-04-06 20:51:06Z] Error submitting event 243841 "Scan of Phraa Pruae IV-Y d7212 A": 402 Item unknown
[2018-04-06 20:51:06Z] Error submitting event 243846 "Scan of Phraa Pruae IV-Y d7212 B": 402 Item unknown
[2018-04-06 20:51:06Z] Error submitting event 243848 "Scan of Phraa Pruae IV-Y d7212 C": 402 Item unknown
[2018-04-06 20:51:06Z] Error submitting event 243849 "Scan of Phraa Pruae IV-Y d7212 D": 402 Item unknown

I wonder if at this point the EDDN message had not yet been sent, and so EDSM had not yet seen these bodies? It does look like you got first discovery on them in EDSM after the submitted entries were re-processed.

There is no folder named 'C:\code\' on my system.

This directory is where EDDiscovery was compiled on the computer of the person who created the installer.

Right at the new start today it logged:

[2018-04-07 13:30:49Z] Running logfile age check
[2018-04-07 13:30:49Z] Native library pre-loader is trying to load native SQLite library "D:\EDDiscovery\x64\SQLite.Interop.dll"...
[2018-04-07 13:30:49Z] SQLite version 3.21.0
[2018-04-07 13:30:50Z] *** Elite Dangerous Discovery Initializing - Version 9.1.9.0 (Using D:\EDDiscovery\), Platform: Win32NT
[2018-04-07 13:30:50Z] Theme ID 10037
[2018-04-07 13:30:52Z] New watch on C:\Users\Eahlstan\Saved Games\Frontier Developments\Elite Dangerous
[2018-04-07 13:30:52Z] Scanned C:\Users\Eahlstan\Saved Games\Frontier Developments\Elite Dangerous
[2018-04-07 13:31:03Z] Failed to add body Eol Prou MR-V d2-640 A 1 to system - too deep
[2018-04-07 13:31:03Z] Failed to add body Eol Prou MR-V d2-640 A 2 to system - too deep
...
[2018-04-07 13:45:58Z] Failed to add body Eol Prou MR-V d2-640 A 1 to system - too deep
[2018-04-07 13:45:58Z] Failed to add body Eol Prou MR-V d2-640 A 2 to system - too deep
[2018-04-07 13:45:58Z] Failed to add body Eol Prou IK-D b14-60 AB 2 to system - too deep
...
[2018-04-07 13:45:58Z] Failed to add body Phaa Chruia XV-E d11-1293 B 3 to system - too deep

Is the EDSM button enabled on the Scan panel? It looks like whichever system this is needs to be cleaned up in EDSM. Either that, or the FSDJump event was missed.

[2018-04-07 13:31:50Z] Thread Star Distance Worker waiting for thread Background Worker Thread to finish writer
[2018-04-07 13:31:50Z] The transaction lock has been held for a long time.
[2018-04-07 13:31:50Z] Thread waiting for thread Background Worker Thread to finish writer
[2018-04-07 13:31:55Z] Start Monitor on C:\Users\Eahlstan\Saved Games\Frontier Developments\Elite Dangerous
[2018-04-07 13:31:55Z] EDSM Fetch logs start with cmdr 1
[2018-04-07 13:31:55Z] EDSM Fetch logs restart time
[2018-04-07 13:31:55Z] EDSM Thread logs start
[2018-04-07 13:31:56Z] Thread Background Worker Thread waiting for readers to finish
[2018-04-07 13:31:57Z] Thread Star Distance Worker waiting for thread Background Worker Thread to finish writer
[2018-04-07 13:31:57Z] Last message repeated 5 times
[2018-04-07 13:31:57Z] The transaction lock has been held for a long time.
[2018-04-07 13:31:57Z] Last message repeated 11 times
[2018-04-07 13:31:57Z] Thread waiting for thread Background Worker Thread to finish writer
[2018-04-07 13:31:57Z] Last message repeated 5 times
[2018-04-07 13:31:57Z] Thread Background Worker Thread waiting for readers to finish
[2018-04-07 13:31:58Z] EDSM Comments downloaded/updated 0
[2018-04-07 13:31:59Z] Thread Background Worker Thread waiting for readers to finish
[2018-04-07 13:31:59Z] Thread Background Worker Thread waiting for readers to finish
[2018-04-07 13:32:44Z] Database locked - retrying
[2018-04-07 13:32:44Z] bei System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
[2018-04-07 13:32:44Z] bei System.Data.SQLite.SQLiteDataReader.NextResult()
[2018-04-07 13:32:44Z] bei System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
[2018-04-07 13:32:44Z] bei System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
[2018-04-07 13:32:44Z] bei EliteDangerousCore.DB.SQLiteDataReaderED`1..ctor(DbCommand cmd, CommandBehavior behaviour, SQLiteTransactionED`1 txn, SQLiteTxnLockED`1 txnlock) in C:\Code\EDDiscovery\EliteDangerous\DB\SQLiteCommandED.cs:Zeile 339.
[2018-04-07 13:32:44Z] bei EliteDangerousCore.DB.SQLiteCommandED`1.ExecuteDbDataReader(CommandBehavior behavior) in C:\Code\EDDiscovery\EliteDangerous\DB\SQLiteCommandED.cs:Zeile 490.
[2018-04-07 13:32:45Z] Thread Background Worker Thread waiting for readers to finish
[2018-04-07 13:32:45Z] Last message repeated 9 times

//reruns of 'Database locked'

This would have been during the Systems DB index rebuild after a sync.

 

[Eahlstan]

Is the EDSM button enabled on the Scan panel?

Yes it is. If I click it it starts sending 730 journal entries. 'Manual EDSM journal sync complete'. I click it it again, it starts syncing 730 journal entries. It's an infinite loop.

[2018-04-07 15:09:51Z] Error submitting event 244046 "Scan of Phraa Pruae MB-X d1-2833 D": 402 Item unknown
[2018-04-07 15:09:51Z] Error submitting event 244047 "Scan of Phraa Pruae MB-X d1-2833 BCD 6": 402 Item unknown

www.edsm.net/en/system/bodies/id/23990087/name/Phraa+Pruae+MB-X+d1-2833
www.elitegalaxyonline.com/system-view/?system_id=1061647

This isn't just for newly scanned systems:

[2018-04-07 15:09:51Z] Error submitting event 186693 "Scan of Splojeia LD-K d8-6552 A": 402 Item unknown
[2018-04-07 15:09:51Z] Error submitting event 186860 "Scan of Splojeia LD-K d8-5032 A": 402 Item unknown
[2018-04-07 15:09:51Z] Error submitting event 186861 "Scan of Splojeia LD-K d8-5032 B": 402 Item unknown
[2018-04-07 15:09:51Z] Error submitting event 186863 "Scan of Splojeia LD-K d8-5032 C": 402 Item unknown
[2018-04-07 15:09:51Z] Error submitting event 186865 "Scan of Splojeia LD-K d8-5032 D": 402 Item unknown

But in this case the bodies in question are known to EDSM:

www.edsm.net/en/system/id/20885625/name/Splojeia+LD-K+d8-5032
www.elitegalaxyonline.com/system-view/?system_id=740304

I didn't even realise that there were problems with EDSM, as I only noticed that the automated sync with EGO and EDDN skipped some bodies.

 

[Bravada Cadelanne]

Yes it is. If I click it it starts sending 730 journal entries. 'Manual EDSM journal sync complete'. I click it it again, it starts syncing 730 journal entries. It's an infinite loop.

[2018-04-07 15:09:51Z] Error submitting event 244046 "Scan of Phraa Pruae MB-X d1-2833 D": 402 Item unknown
[2018-04-07 15:09:51Z] Error submitting event 244047 "Scan of Phraa Pruae MB-X d1-2833 BCD 6": 402 Item unknown

www.edsm.net/en/system/bodies/id/23990087/name/Phraa+Pruae+MB-X+d1-2833
www.elitegalaxyonline.com/system-view/?system_id=1061647

This isn't just for newly scanned systems:

[2018-04-07 15:09:51Z] Error submitting event 186693 "Scan of Splojeia LD-K d8-6552 A": 402 Item unknown
[2018-04-07 15:09:51Z] Error submitting event 186860 "Scan of Splojeia LD-K d8-5032 A": 402 Item unknown
[2018-04-07 15:09:51Z] Error submitting event 186861 "Scan of Splojeia LD-K d8-5032 B": 402 Item unknown
[2018-04-07 15:09:51Z] Error submitting event 186863 "Scan of Splojeia LD-K d8-5032 C": 402 Item unknown
[2018-04-07 15:09:51Z] Error submitting event 186865 "Scan of Splojeia LD-K d8-5032 D": 402 Item unknown

But in this case the bodies in question are known to EDSM:

www.edsm.net/en/system/id/20885625/name/Splojeia+LD-K+d8-5032
www.elitegalaxyonline.com/system-view/?system_id=740304

I didn't even realise that there were problems with EDSM, as I only noticed that the automated sync with EGO and EDDN skipped some bodies.

https://github.com/EDDiscovery/EDDiscovery/pull/1901 should prevent the EGO and EDDN messages from being lost when EDSM errors out.

 

[Eahlstan]

https://github.com/EDDiscovery/EDDiscovery/pull/1901 should prevent the EGO and EDDN messages from being lost when EDSM errors out.

As I'm not familiar with these kind of things: Can I get this by myself or is this something that's going to be in the next release?

 

[Eahlstan]

I just noticed that there are a bunch of EDDN errors too, relating some of the systems causing the EDSM errors (but not all EDSM errors have correspondening EDDN errors).

eg:

[2018-04-07 21:34:17Z] EDDN message post failed - status: BadRequest
[2018-04-07 21:34:17Z] Response: FAIL: [<ValidationError: "u'' is too short">]
[2018-04-07 21:34:17Z] EDDN Message: {


[2018-04-07 21:34:17Z] "header": {


[2018-04-07 21:34:17Z] "uploaderID": "Eahlstan",


[2018-04-07 21:34:17Z] "softwareName": "EDDiscovery",


[2018-04-07 21:34:17Z] "softwareVersion": "9.1.9.0"


[2018-04-07 21:34:17Z] },


[2018-04-07 21:34:17Z] "$schemaRef": "https://eddn.edcd.io/schemas/journal/1",


[2018-04-07 21:34:17Z] "message": {


[2018-04-07 21:34:17Z] "timestamp": "2017-08-23T20:46:58Z",


[2018-04-07 21:34:17Z] "event": "Scan",


[2018-04-07 21:34:17Z] "BodyName": "Blu Euq YJ-A d27",


[2018-04-07 21:34:17Z] "DistanceFromArrivalLS": 0.0,


[2018-04-07 21:34:17Z] "StarType": "F",


[2018-04-07 21:34:17Z] "StellarMass": 1.421875,


[2018-04-07 21:34:17Z] "Radius": 870287616.0,


[2018-04-07 21:34:17Z] "AbsoluteMagnitude": 3.710999,


[2018-04-07 21:34:17Z] "Age_MY": 1614,


[2018-04-07 21:34:17Z] "SurfaceTemperature": 6683.0,


[2018-04-07 21:34:17Z] "RotationPeriod": 203676.328125,


[2018-04-07 21:34:17Z] "AxialTilt": 0.0,


[2018-04-07 21:34:17Z] "StarSystem": "",


[2018-04-07 21:34:17Z] "StarPos": [


[2018-04-07 21:34:17Z] 156.34375,


[2018-04-07 21:34:17Z] 170.8125,


[2018-04-07 21:34:17Z] 4099.0


[2018-04-07 21:34:17Z] ]


[2018-04-07 21:34:17Z] }


[2018-04-07 21:34:17Z] }


Most of my sytems get synced to EDDN and EDSM, but noticing the timestamp this problem seems to be going under my radar for at least months.

 

[Bravada Cadelanne]

I just noticed that there are a bunch of EDDN errors too, relating some of the systems causing the EDSM errors (but not all EDSM errors have correspondening EDDN errors).

eg:

[2018-04-07 21:34:17Z] EDDN message post failed - status: BadRequest
[2018-04-07 21:34:17Z] Response: FAIL: [<ValidationError: "u'' is too short">]
[2018-04-07 21:34:17Z] EDDN Message: {
[2018-04-07 21:34:17Z]   "header": {
[2018-04-07 21:34:17Z]     "uploaderID": "Eahlstan",
[2018-04-07 21:34:17Z]     "softwareName": "EDDiscovery",
[2018-04-07 21:34:17Z]     "softwareVersion": "9.1.9.0"
[2018-04-07 21:34:17Z]   },
[2018-04-07 21:34:17Z]   "$schemaRef": "https://eddn.edcd.io/schemas/journal/1",
[2018-04-07 21:34:17Z]   "message": {
[2018-04-07 21:34:17Z]     "timestamp": "2017-08-23T20:46:58Z",
[2018-04-07 21:34:17Z]     "event": "Scan",
[2018-04-07 21:34:17Z]     "BodyName": "Blu Euq YJ-A d27",
[2018-04-07 21:34:17Z]     "DistanceFromArrivalLS": 0.0,
[2018-04-07 21:34:17Z]     "StarType": "F",
[2018-04-07 21:34:17Z]     "StellarMass": 1.421875,
[2018-04-07 21:34:17Z]     "Radius": 870287616.0,
[2018-04-07 21:34:17Z]     "AbsoluteMagnitude": 3.710999,
[2018-04-07 21:34:17Z]     "Age_MY": 1614,
[2018-04-07 21:34:17Z]     "SurfaceTemperature": 6683.0,
[2018-04-07 21:34:17Z]     "RotationPeriod": 203676.328125,
[2018-04-07 21:34:17Z]     "AxialTilt": 0.0,
[2018-04-07 21:34:17Z]     "StarSystem": "",
[2018-04-07 21:34:17Z]     "StarPos": [
[2018-04-07 21:34:17Z]       156.34375,
[2018-04-07 21:34:17Z]       170.8125,
[2018-04-07 21:34:17Z]       4099.0
[2018-04-07 21:34:17Z]     ]
[2018-04-07 21:34:17Z]   }
[2018-04-07 21:34:17Z] }

What happens if you go Admin -> Re-scan all journal files, then try syncing the EDDN / EDSM bodies again?

 

[Eahlstan]

What happens if you go Admin -> Re-scan all journal files, then try syncing the EDDN / EDSM bodies again?

This didn't change anything.

 

[gazelle]

[2018-04-07 21:34:17Z] EDDN message post failed - status: BadRequest
[2018-04-07 21:34:17Z] Response: FAIL: [<ValidationError: "u'' is too short">]

-> [2018-04-07 21:34:17Z] "StarSystem": "",

The message is missing the systemname (u'' means empty unicode string).

 

[Bravada Cadelanne]

This didn't change anything.

The empty system name suggests the systems DB is probably corrupt. Please try holding shift while starting the program, clicking "Delete/Rebuild System DB", then clicking Run.

 

[Eahlstan]

The empty system name suggests the systems DB is probably corrupt. Please try holding shift while starting the program, clicking "Delete/Rebuild System DB", then clicking Run.

Did this, sadly still nothing changed.