This object is in archive! 

Server Log Massive Epic(Games) Spam

Greg House shared this bug 2 years ago
Won't Fix

Looking for issues in the log, but find an incredible number of these and closely related. the log is too big to paste here...


2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 32 (Found bundle for host api.epicgames.dev: 0x23b0ab88440 [can pipeline])

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 33 (No more connections allowed to host: 16)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 34 (No connections available.)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 35 (Found bundle for host api.epicgames.dev: 0x23b0ab88440 [can pipeline])

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 36 (No more connections allowed to host: 16)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 37 (No connections available.)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 38 (Found bundle for host api.epicgames.dev: 0x23b0ab88440 [can pipeline])

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 39 (No more connections allowed to host: 16)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 40 (No connections available.)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 41 (Found bundle for host api.epicgames.dev: 0x23b0ab88440 [can pipeline])

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 42 (No more connections allowed to host: 16)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 43 (No connections available.)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 44 (Found bundle for host api.epicgames.dev: 0x23b0ab88440 [can pipeline])

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 45 (No more connections allowed to host: 16)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 46 (No connections available.)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 47 (Found bundle for host api.epicgames.dev: 0x23b0ab88440 [can pipeline])

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 48 (No more connections allowed to host: 16)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 49 (No connections available.)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 0 (Found bundle for host api.epicgames.dev: 0x23b0ab88440 [can pipeline])

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 1 (No more connections allowed to host: 16)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 2 (No connections available.)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 3 (Found bundle for host api.epicgames.dev: 0x23b0ab88440 [can pipeline])

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 4 (No more connections allowed to host: 16)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 5 (No connections available.)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 6 (Found bundle for host api.epicgames.dev: 0x23b0ab88440 [can pipeline])

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 7 (No more connections allowed to host: 16)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 8 (No connections available.)

2022-03-11 15:28:55.650 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 9 (Found bundle for host api.epicgames.dev: 0x23b0ab88440 [can pipeline])

2022-03-11 15:28:55.651 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 10 (No more connections allowed to host: 16)

2022-03-11 15:28:55.651 - Thread: 20 -> EOS|LogHttp: 0000023C6ECC6D50: libcurl info message cache 11 (No connections available.)

Replies (3)

photo
1

2022-03-11 15:28:55.653 - Thread: 20 -> EOS|LogHttp: Lockout of 3.170934s on https://api.epicgames.dev/auth/v1/oauth/token

2022-03-11 15:28:55.653 - Thread: 20 -> EOS|LogHttp: Lockout of 3.500046s on https://api.epicgames.dev/auth/v1/oauth/token

2022-03-11 15:28:55.653 - Thread: 20 -> EOS|LogHttp: Lockout of 3.122837s on https://api.epicgames.dev/auth/v1/oauth/token

2022-03-11 15:28:55.653 - Thread: 20 -> EOS|LogHttp: Lockout of 3.379864s on https://api.epicgames.dev/auth/v1/oauth/token

2022-03-11 15:28:55.653 - Thread: 20 -> EOS|LogHttp: Lockout of 3.364360s on https://api.epicgames.dev/auth/v1/oauth/token

2022-03-11 15:28:55.653 - Thread: 20 -> EOS|LogHttp: Lockout of 3.748894s on https://api.epicgames.dev/auth/v1/oauth/token

2022-03-11 15:28:55.653 - Thread: 20 -> EOS|LogHttp: Lockout of 2.767785s on https://api.epicgames.dev/auth/v1/oauth/token


Is SE dDOS'ing something?

photo
1

Hello Engineer,


Could you please describe what actions you were taking at the time of this log spam? Were you connecting to an EOS server, actively playing on it?

Could you please try sending us a log via the in-game method? To send the log:


Reproduce the issue or circumstances of the issue.


Open the Help Menu by pressing Y in the Main Menu.


Select the Report Issue tab.


Fill in the contact info.


Post a message to this ticket with that contact info so that we could find your log.


Thank you.


Kind regards,


Keen Software House: QA Department

photo
1

Hello, Engineer!

Because there is no new comment from you, and we are unable to reproduce the issue on our own, I will close this thread now as outdated.

If you or any other player will experience this issue again, please make a new thread and provide all needed info there.

Thank you for understanding.

Kind Regards

Keen Software House: QA Department

Replies have been locked on this page!