Hi there,
I’m having some issues getting my server spun up. Wondering if anyone can lend advice
I’m using the Multiplay Linux SDK with an Unreal 5.1 dedicated server project, compiling to a Linux build.
The issues I’m encountering are
- Cannot see server logs on the Multiplay dashboard
- Server crashes moments after startup
My launch parameters are set like so:
-port=$$port$$ -LOG=../../../../$$log_dir$$/$$serverid$$.log -queryPort $$query_port$$ -queryType $$query_type$$
The server crash -
And these are the blueprints which live inside the game (server) map - so not in the entry (client) map -
Best,
Maria
To fix the missing logs you should change your build configuration flag:
-LOG=../../../../$$log_dir$$/$$serverid$$.log
should be:
-logFile=$$log_dir$$/$$serverid$$.log.
I’m not familiar with the visual coding you are using there, someone else might be, but the Query DOWN log messages seem to indicate that you haven’t initialised SQP at server startup. Try the change above which might give you some log messages to follow and report back if you need more help
My apologies, I was assuming you were using the Unity engine for your game. My instructions for the log path are, therefore, incorrect.
Instead, I recommend you take a look at this documentation page Redirect log output for games using Unreal for setting up logs for Unreal engine games, and this video for further guidance:
https://www.youtube.com/watch?v=IfOMlH8BzCs
I apologise for providing incorrect advice and I hope this new advice can help you. Feel free to reach out once more if you have questions or queries
Hey thanks for the suggestion, sadly -logFile=$$log_dir$$/$$serverid$$.log doesn’t produce logs either
For the launch parameters I followed these instructions Launch parameters
Wondering how to initialise SQP at server startup as you suggest. I haven’t created any Server Query Handler Subsystem nodes yet so will try that. (You mentioned you’re not familiar with Unreal blueprints so putting this here in case anyone else can pick it up)
I didn’t include a screenshot of the Server Config Subsystem blueprint, here it is.
Thanks for reminding me about the above tutorial, I now have the logs!
-port=$$port$$ -queryPort=$$query_port$$ -log=../../../../..$$log_dir$$ENGINE.log is the correct way to format the launch parameters.
Have attached the log.
Specifically some time after the engine initialisation I see a fatal error. I can confirm that this build runs successfully locally.
[2023.02.15-16.55.03:676][ 0]LogLoad: (Engine Initialization) Total time: 2.77 seconds
[2023.02.15-16.59.02:090][132]LogCore: === Critical error: ===
Unhandled Exception: SIGSEGV: invalid attempt to read memory at address 0x0000000000000000
[2023.02.15-16.59.02:091][132]LogCore: Fatal error!
0x00007f028af2123f libc.so.6!clock_nanosleep(+0xdf)
0x00007f028af26ec7 libc.so.6!nanosleep(+0x16)
0x00007f028af5985f libc.so.6!usleep(+0x4e)
0x0000000009c4b174 STREAMServer-Linux-Debug!
8809255–1198243–server_43967858_logs_20230215165929.zip (14.2 KB)
Hey @maria-marshmallow It looks to be a Memory read error as shown
This message usually indicates that an unhandled exception has occurred during game server run. Looking further, we see “SIGSEGV” is the core error, this indicates that it is caused by an invalid attempt to write to memory
This could occur from multiple reasons, being a possible stack corruption, a buffer overflow happening in the game code, or a null pointer reference; what I mean by these, is that somewhere in your program, it is trying to access a memory location that it shouldn’t be accessing - potentially causing by a bug in the program.
I’d recommend checking over your code for any bugs, the Unreal forums themselves could also assist with this error.
Hey @maria-marshmallow , we are also running into this exact same crash on Unreal 5.1, multiplay linux dedicated servers. Although our servers crash randomly during a match and only sometimes, so it isn’t a boot crash for us. Were you able to resolve the issue or have any other insight that would be helpful?
