Problems starting the server and getting the log file

Hi. We are using Unreal Engine and Legacy Multiplayer fro game. The client launches the game using UPlayFabClientAPI::StartGame (from marketplace PlayFab plugin). After moving from ue4.22 to ue4.24, we cannot connect to the server, or the server cannot started successfully. When the game starts, the client receives a valid response from PlayFab with connecting information (LobbyID, ServerHostname, ServerIPV4Address, ServerPort and other). But the server is shutting down a few seconds after starting. Unable to connect to it. There are no logs in the Archived Games section.

Everything works fine in the local docker container.

We included in the build all the dependencies that tool "ListDlls" showed. The folder for the logs is set via the start parameter "-ABSLOG = <log_file_path>".

Also we tried to launch an empty blueprint ue4.24 project. It started and worked for several minutes until it was turned off manually. An empty ue4.24 project with C ++ code did not start. But PlayFab returned an Internal server error. Also we can't get log file from empty server's build ue4.24, but we know for sure that it runs correctly, since it responds to connection requests.

How can we understand the reason why the server crashes or not started?

Last build version HG_Server_0212_03

TitleID 7978A

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Citrus Yan commented · Feb 13, 2020 at 03:07 AM

Does it mean that everything works fine in UE4.22 (server won't crash or not started, logs are available in Archived Game Section)?

And, which PlayFab SDK version did you use for UE4.24?

0 ·

Viktor Kovylin Citrus Yan commented · Feb 13, 2020 at 08:50 AM

Yes, server is starting. We connected and played the game. Logs were available.

We don't use GSDK. Only PlayFab marketplace plugin latest version (1.31.200121). The plugin was updated with the version of the engine.

0 ·

Viktor Kovylin Citrus Yan commented · Feb 13, 2020 at 04:02 PM

Maybe logs exist, but for some reason they are not saved to the folder at <log_file_path>.

If possible, can you put the files from \HeadGun\Saved\Logs\ folder in the Output files for any archived game?

For example:

Build: HG_Server_0212_03

Lobby: 5389B09D167D41B2

0 ·

Citrus Yan Viktor Kovylin commented · Feb 14, 2020 at 05:45 AM

Unfortunately, I cannot do that.

And, I checked your build settings page, looks like you did not change the command-line arguments "-log_file_path=<log_file_path>" to "-ABSLOG=<log_file_path>" for your unreal server build HG_Server_0212_03. That might be the reason why you didn't receive the logs. Will you change that and test again to see whether it'll work well?

0 ·

Show more comments

Viktor Kovylin Citrus Yan commented · Feb 14, 2020 at 06:21 PM

We uploaded the server build to Servers 2.0. Connect via RDP to virtual machine. Launched the game server manually. See the error that dll is missing (vcruntime140_1.dll). Put this dll. Launched again. And it worked.

After that, we uploaded the same build (with dll) to Legacy Multiplayer. It did not start. Why?

Legacy Multiplayer build name: HG_Server_0214_01_140_1

Servers 2.0 build name: HG_140_1

0 ·

Citrus Yan Viktor Kovylin commented · Feb 17, 2020 at 08:35 AM

Ah, I see. Well, Legacy Multiplayer runs on Windows Server 2K12 R2, while Server 2.0 runs on Window Server 2019, these environments are a bit different, will you try manually launch the game server on Windows Server 2K12 R2 and see what happens?

0 ·

question

Problems starting the server and getting the log file

0 Answers

Write an Answer

Navigation

Spaces

question details