Abandoned [App] edproxy - Remote the ED netLog to multiple listeners

Gen.Fussypants

Gen.Fussypants
@silence please

Well crap. I thought I covered that base. I will look into it today and hopefully have an update by the end of today. Thank you for looking into it! Also, thank you for creating a Jira issue!
 

silence please

S
Gen.Fussypants said:
@silence please

Well crap. I thought I covered that base. I will look into it today and hopefully have an update by the end of today. Thank you for looking into it! Also, thank you for creating a Jira issue!
Click to expand...

No worries - I just now noticed that people mentioned the "no start" issue on the first page; this is the cause for it.

Really love the picture renaming feature; I had done a silly bash script in cygwin for exactly that since I wanted my exploration screenshots named by system but it wasn't terribly efficient.

I took 2.0.2 for a spin with an AndDiscovered client and ran into some situations that edproxy wouldn't list the device as connected all of a sudden yet the tablet said it was - I'll investigate later with a packet sniffer active, see how to reproduce this accurately and put up a Jira issue either for edproxy or AndDiscovered depending on which seems to be causing it.
 

Gen.Fussypants

Gen.Fussypants
Yeah, I experienced some of this too after release. I have a development version that now implements a heartbeat with edproxy. These situations should now be resolved. The problem is that I am not reliably getting an exception when the TCP socket is closed on one end.

Ah, the perks of having no QA team. I haven't flown solo like this in ages. Very invigorating, and frustrating at the same time. Thank you again for banging on the tool. The more eyes, and hands, willing to experiment and actually report issues the better the tool will be.
 

Gen.Fussypants

Gen.Fussypants
Version 2.0.3:
* Fixed startup issue where the .edproxy did not exist so the application would crash.
* Added 'Heartbeat' flag to 'Init' message. This is optional and will function without a heartbeat.
* Added 'Heartbeat' message type.
** A client sends a heartbeat at an assigned (better to be a few seconds before) interval. If edproxy misses two heartbeats in a row then it will close down the connection.

Big thank you to @silence_please for looking into the root cause!
 
Last edited:

Gen.Fussypants

Gen.Fussypants
Version 2.0.4:
* Fixed several crashes, or lockups, due to networking
* Fixed High Resolution images not being converted.
* Added new Ping/Pong heartbeat so both Edproxy and clients may react faster to disconnects.
 

john211murphy

J
I'm unable to get any data to display on the "AndDiscovery" android app. I think i've go the EDproxy working OK. The Android App is shown to connect but the "Import" section is greyed out. I cant get any Screenshots to work either. The paths look correct.
Can anyone help?
 

Gen.Fussypants

Gen.Fussypants
I would absolutely be happy to help. Can you PM the following:

1) What version of AndDiscovered and Edproxy are you on?
2) Within AndDiscovered under 'Settings' how many 'Display Days' do you have set?
3) Do you have a 'green' icon in AndDiscovered and an IP address showing in Edproxy?

'Import' is a work in progress and is not finished. I disabled it for now, and hope to have it ready soon. It is meant for importing in EDDiscovery or Captain's Log in the future.
 

john211murphy

J
Gen.Fussypants said:
I would absolutely be happy to help. Can you PM the following:

1) What version of AndDiscovered and Edproxy are you on?
2) Within AndDiscovered under 'Settings' how many 'Display Days' do you have set?
3) Do you have a 'green' icon in AndDiscovered and an IP address showing in Edproxy?


'Import' is a work in progress and is not finished. I disabled it for now, and hope to have it ready soon. It is meant for importing in EDDiscovery or Captain's Log in the future.
Click to expand...


Thank you for your reply.

1) I am running EDproxy v.2.0.4 and AndDiscovered direct from the Play Store.
2) I have tried several setting of "Display Days" from 1 to its Max.
3) The Green light Icon is bright and the Android Device is showing on Edproxy.

When AndDiscover starts up, it displays a message saying "No systems to show".


Regards.
 

Gen.Fussypants

Gen.Fussypants
I am glad you got your issue resolved. Any feedback would be greatly appreciated! Always looking to make the tools more useful for people.
 

Gen.Fussypants

Gen.Fussypants
Version 2.1.2:
- New support for 3rd party plugins!
** Support is limited to those items included by hand currently. Sorry to say this is not truly dynamic yet.
** Added new View into active 3rd party plugins.
- Support for EDSM 3rd party plugin
** Cloud based storage for all the systems you have visited!
** Edproxy is designed to only *read* the netLog. Thus it does not have a concept of exploration notes or anything like that. Here we are *only* sending the systems you have visited just like Edproxy currently events out to listening applications.

How to setup Edproxy to transmit your system logs to EDSM
1. Go create an EDSM (www.edsm.net) account.
2. Look in your Account settings for your API Key.
3. Open Edproxy->Settings (MacOSx->Preferences)
4. Enter your API key AND the commander name you registered.
5. Click OK!
6. If you have auto-start on then Edproxy will automatically Stop then Start the server. Otherwise click on the "Start" button.

If you have a lot of systems in your log file the initial upload may take a very long time depending where you are in the world. It could be more than 30 minutes to get everything up-to-date. HOWEVER, you do NOT have to wait! Edproxy remembers where you are in the update process so even if you close the application, and restart, it will begin the update from where you left off. Also, you do NOT need to wait for it to finish to continue your exploration, or movement in the game. Edproxy will automatically send out all systems in order until it has caught up with your current location.
 

Kaspur

K
I've entered all information to connect to EDSM, but EDproxy isn't sending any logs (I'm monitoring the network traffic), even though it has status "transmitting".
 

Gen.Fussypants

Gen.Fussypants
Can you try doing a "Stop" then "Start" again? I was stressing it some this evening and I ran into a similar issue. I am still investigating as to why that would occur.

Also, in your <user directory>/.edproxy you will find a file named "edsm.ini". Look in there and see if the "last time" and "last system" are being updated. In that same folder is the "edproxy.log". This may contain information about what is being transmitted.

You may also look at EDSM directly. Under your account you can view all of your "exploration logs". These are the systems you have traveled to that Edproxy has reported. If that is not current then you are transmitting.

Note: Do not share the "edsm.ini" file as it contains your API key.
 

Kaspur

K
Gen.Fussypants said:
Can you try doing a "Stop" then "Start" again? I was stressing it some this evening and I ran into a similar issue. I am still investigating as to why that would occur.

Also, in your <user directory>/.edproxy you will find a file named "edsm.ini". Look in there and see if the "last time" and "last system" are being updated. In that same folder is the "edproxy.log". This may contain information about what is being transmitted.

You may also look at EDSM directly. Under your account you can view all of your "exploration logs". These are the systems you have traveled to that Edproxy has reported. If that is not current then you are transmitting.

Note: Do not share the "edsm.ini" file as it contains your API key.
Click to expand...
Stop and start didn't have any effect. Last time and Last system in the edsm.ini are empty. This is the last part of my log:
Code: 
2015-11-13 08:55:41,693-DEBUG-<string>-321    New Plugin (EDSM) has been added.
2015-11-13 08:55:41,693-DEBUG-<string>-394    Done plugins
2015-11-13 08:55:41,882-DEBUG-ednet.py-132    Sending: [Discovery Message: Type [Announce], Name [edproxy], IPv4 [192.168.0.102], Port [45550]]
2015-11-13 08:55:41,977-DEBUG-<string>-323    Parse old logs.
2015-11-13 08:55:44,523-DEBUG-<string>-148    Stop discovery service
2015-11-13 08:55:44,938-DEBUG-<string>-150    Stop Proxy server
2015-11-13 08:55:45,272-INFO-ednet.py-268    Exiting proxy server listen thread.
2015-11-13 08:55:45,272-DEBUG-<string>-152    Stop netlog parser
2015-11-13 08:55:45,272-DEBUG-<string>-154    Stop image acquisition service
2015-11-13 08:55:45,272-DEBUG-<string>-157    Stop all proxy clients and 3rd party plugins
2015-11-13 08:55:45,273-DEBUG-<string>-170    All services stopped
2015-11-13 08:55:45,296-DEBUG-<string>-387    Starting up plugins.
2015-11-13 08:55:45,302-DEBUG-<string>-389    Plugin EDSM:True
2015-11-13 08:55:45,315-DEBUG-<string>-321    New Plugin (EDSM) has been added.
2015-11-13 08:55:45,315-DEBUG-<string>-394    Done plugins
2015-11-13 08:55:45,375-DEBUG-ednet.py-132    Sending: [Discovery Message: Type [Announce], Name [edproxy], IPv4 [192.168.0.102], Port [45550]]
2015-11-13 08:55:45,398-DEBUG-<string>-323    Parse old logs.
2015-11-13 08:55:47,851-DEBUG-<string>-148    Stop discovery service
2015-11-13 08:55:47,887-DEBUG-<string>-150    Stop Proxy server
2015-11-13 08:55:48,339-INFO-ednet.py-268    Exiting proxy server listen thread.
2015-11-13 08:55:48,339-DEBUG-<string>-152    Stop netlog parser
2015-11-13 08:55:48,339-DEBUG-<string>-154    Stop image acquisition service
2015-11-13 08:55:48,339-DEBUG-<string>-157    Stop all proxy clients and 3rd party plugins
2015-11-13 08:55:48,341-DEBUG-<string>-170    All services stopped
2015-11-13 08:55:49,809-DEBUG-<string>-387    Starting up plugins.
2015-11-13 08:55:49,819-DEBUG-<string>-389    Plugin EDSM:True
2015-11-13 08:55:49,828-DEBUG-<string>-321    New Plugin (EDSM) has been added.
2015-11-13 08:55:49,828-DEBUG-<string>-394    Done plugins
2015-11-13 08:55:49,871-DEBUG-ednet.py-132    Sending: [Discovery Message: Type [Announce], Name [edproxy], IPv4 [192.168.0.102], Port [45550]]
2015-11-13 08:55:49,903-DEBUG-<string>-323    Parse old logs.
 

Gen.Fussypants

Gen.Fussypants
@Kaspur

Careful with posting the log. It might contain your API key at some point. You can always forward the log to me at fussyware@gmail.com, or just a PM to me.

It would seem that it is blocking in the parsing of the historic log data. In fact given what is in the log no data is being processed. I am looking into why this might be the case, but for now I have a couple questions.

1) Have you used Edproxy before? Everything worked normally?
2) Verbose logging in the netLog has been turned on before now? Edproxy will automatically turn it on, but if it was not on before there will be no historical data.
 

Gen.Fussypants

Gen.Fussypants
To the folks upgrading to 64-bit:
Don't forget to change your "NetLog" path in Preferences so that it points to the new Log directories. I also advise copying your old log files over to the new location.
 
You must log in or register to reply here.
Back
Top Bottom