search

FakeByte / EpicOnlineTransport

A Transport for Mirror using Epic Online Services
MIT License
252 stars 52 forks source link

EOS not initialized (Linux) #16

Closed DanielTizon closed 3 years ago

DanielTizon commented 3 years ago

After configure everything, I'm getting this message:

EOS not initialized. Server could not be started
Epic Manager: Category - LogEOS Message - Updating Platform SDK Config, Time: 1.6
Epic Manager: Category - LogEOS Message - SDK Config Platform Update Request Successful, Time: 1.9
Epic Manager: Category - LogEOSAnalytics Message - Start Session (User: ...)
Epic Manager: Unknown log processing. Category - LogEOSAnalytics Message - Record Event: EOSSDK.HTTP.Complete <Redacted>
Epic Manager: Category - LogEOS Message - Updating Product SDK Config, Time: 1.9
Epic Manager: Unknown log processing. Category - LogEOSAnalytics Message - Record Event: EOSSDK.HTTP.Complete <Redacted>
Epic Manager: Unknown log processing. Category - LogEOSConnect Message - ConnectClientAuthTask Success
Epic Manager: Unknown log processing. Category - LogEOSAnalytics Message - Record Event: EOSSDK.HTTP.Complete <Redacted>
Epic Manager: Category - LogEOS Message - SDK Config Product Update Request Successful, Time: 2.1
Epic Manager: Category - LogEOS Message - SDK Config Data - Watermark: 8322246731
Epic Manager: Category - LogEOS Message - ScheduleNextSDKConfigDataUpdate - Time: 2.133228, Update Interval: 358.460602
Epic Manager: Unknown log processing. Category - LogEOSAnalytics Message - Record Event: EOSSDK.HTTP.Complete <Redacted>
Epic Manager: Category - LogEOSMessaging Message - Attempting connection to Stomp. LocalUserId=[000...19a] Url=[<Redacted>]
Connect Interface Login succeeded
EOS User Product ID: xxxxxxxxxxx
Epic Manager: Unknown log processing. Category - LogEOSP2P Message - Using Port Range 7777-7876 for P2P traffic
Epic Manager: Unknown log processing. Category - LogEOSAnalytics Message - Record Event: EOSSDK.HTTP.Complete <Redacted>
Epic Manager: Unknown log processing. Category - LogEOSP2P Message - Applying updated RTC Configuration
Epic Manager: Category - LogEOSMessaging Message - Succesfully connected to Stomp. LocalUserId=[000...19a]
Epic Manager: Unknown log processing. Category - LogEOSMessaging Message - Stomp subscribed to topic /xxxxxxxxxxxx/account/xxxxxxxxxx

I have double checked that every product configuration has been correctly applied. And everything was working perfectly with Mirror (kcp transport) before start doing these changes.

Any idea what could be wrong?

Thanks!

FakeByte commented 3 years ago

Did you get the "Login Successful" message? If not then there should be an error message or you started the server before the login was finished.

DanielTizon commented 3 years ago

I'm getting first the message "EOS not initialized." and after that I get the message "Connect Interface Login succeeded". But I tried check "Delayed Initialization" in EOSSDK Component, but it started to fail with error messages:

NullReferenceException: Object reference not set to an instance of an object
  at EpicTransport.EOSSDKComponent.Tick () [0x00016] in <2bb5c4338b113b4bbaa4fagc2g35b562>:0 
  at EpicTransport.EosTransport.ServerEarlyUpdate () [0x00000] in <2bb5c4338b113b4bbaa4fagc2g35b562>:0 
  at Mirror.NetworkServer.NetworkEarlyUpdate () [0x0000d] in <2bb5c4338b113b4bbaa4fagc2g35b562>:0 
  at Mirror.NetworkLoop.NetworkEarlyUpdate () [0x00000] in <2bb5c4338b113b4bbaa4fagc2g35b562>:0

What Unity, Mirror, and EOS SDK are you using?

I'm using:

Unity 2020.3.3f1 Mirror: 36.0.0 EOS SDK v1.11

FakeByte commented 3 years ago

Use the default settings and only start a server after the login is successfull, you can start a coroutine that will wait until EOSSDKComponent.initialized == true. Delayed initialization is only used if you first get an authentication token from a 3rd party service and you need to wait until it arrives before you can do the initialization.