UE 5 Dedicated Server don't add stack trace in crash logs

[toxic zenith]

Hello,

I’m facing an issue where my dedicated server runs normally on PlayFab and I can retrieve the logs when the server finishes execution properly. However, when the server crashes, the log only shows something like:

[295]LogCore: Fatal error!
0x000000000b261995 ChromaTowerServer-Linux-Shipping!?????????????()

An important note: when I run the same Docker image locally, the game also crashes (due to PlayFab GSDK), but in this case, the stack trace appears correctly. This suggests the issue with the missing stack trace only happens when the server runs inside PlayFab.
My dedicated server uses a Docker image based on ubuntu:22.04. I’ve already tried several suggestions found during my research, but none of them solved the problem. Here's a summary of what I’ve tested:

• Confirmed that .sym and .debug files are included in the Docker image.
• Tested both Shipping and Development builds, and have the same result in both.
• Added the following lines to ServerTarget.Target.cs

    bUseLoggingInShipping = true;
    bUseChecksInShipping = true;
    bForceEnableExceptions = true;
    bUsePDBFiles = true;
    GlobalDefinitions.Add("STRIP_SYMBOLS=0");

• Added <bStripSymbolsOnLinux>false</bStripSymbolsOnLinux> in the BuildConfiguration.xml.

Additionally, Is it possible to configure the PlayFab server build to generate core dump files upon crash and make them available for download? This would be very helpful for debugging purposes.
Could you help me with this issue?

In case it's relevant, here's my dockerfile content.

FROM ubuntu:22.04

# Unreal refuses to run as root user, so we must create a user to run as
# Docker uses root by default
RUN useradd --system ue
USER ue

#gameport
EXPOSE 7777/udp
 
#onlineBeaconPort
EXPOSE 7788/tcp

#onlineBeaconPortUDP
EXPOSE 7788/udp

WORKDIR /server

COPY --chown=ue:ue . /server
USER root

# Cria diretório de logs fallback local (opcional)
RUN mkdir -p /server/logs && chown -R ue.ue /server/logs

CMD chown -R ue.ue ${PF_SERVER_LOG_DIRECTORY:-/server/logs} && su ue -c ./ChromaTowerServer.sh

[lofty gate]

@austere vortex I'm sorry for the ping, but we haven't been able to get any support for this issue and have ran out of options to try and solve it after 3 weeks.
@dapper osprey is the dev tasked with solving this currently and has managed to reproduce the issue on a LMA. However, we've tried all we could think of to get the actual logs to no avail.
Could you enlighten us or maybe point us to somebody who could aid?

[austere vortex]

Hi, I'm not an expert on dedicated servers so I probably can't answer everything for you.

I don't know why there's a difference in the call stack logging between local and on PlayFab.

For crash dumps, from what I can see that is supported on Windows container servers, but not linux.
https://learn.microsoft.com/en-us/gaming/playfab/multiplayer/servers/crash-dump-collection

I saw some comments about using a custom startup script to symlink the Unreal 'saved' folder to GDSK log directory and then enable crash dump mode in Unreal.
https://learn.microsoft.com/en-us/gaming/playfab/multiplayer/servers/vmstartupscript