Server Builds Linux failing after upgrade to unity 6

our project was doing fine in unity 2021 lts , but management asked to try what would happen if we try to upgrade to unity 6, well it just wont work, this is the “error” :

Caught fatal signal - signo:11 code:1 errno:0 addr:0x20
Obtained 6 stack frames.
#0  0x007eb61d06f45d in (Unknown)
#1  0x007eb61d06e697 in (Unknown)
#2  0x007eb61d06db08 in (Unknown)
#3  0x007eb61d2e17da in PlayerMain(int, char**)
#4  0x007eb61bae3083 in __libc_start_main
#5  0x006413828cc029 in (Unknown)
2025-01-13 16:43:51,024 INFO exited: metaverse (terminated by SIGSEGV (core dumped); not expected)

please give us some sort of beacon cause we are really in the dark right now

Try deleting Library folder after such a huge jump, and make sure to make a clean build ie don’t export to an already existing build folder. And make a development build if this isn’t already one.

Curiously I saw that exact stacktrace before here, and I think that also was a linux build. Try searching for it, can’t recall whether it got resolved.

It crashes before it even starts, right?

i will try, thanks for the insight.
i will update you after the test

@CodeSmile unfortunatelly the solution you provided doesnt fix at all this issue, error still persist, im still in the dark, can someone of the engineer can take a look at it ? thanks

If you have Enterprise level customer support, you’ll have a representative that you can contact. Otherwise, you will highly unlikely get someone to look at your problem specifically.

What I would do in your case is to take the original 2021 project version, and upgrade it to 2021.3.(latest patch release) if you aren’t using the latest patch. If that works, take that project up to 2022.3.(latest) and try again. If that works, try 6000.0.(latest) again.

Basically try to narrow down the version where the build starts to fail. You may even want to try 2022.1 and 2022.2 as well as 6000.1 beta. If you narrow down the version where it begins to fail, at least you can then go through the changelog for any hints as to what may have changed. Could be a setting, a compatibility issue, and so on.

Also, actually before I’d start doing that I would investigate the currently failing version some more. Quite often such a failure may be attributable to a single Player Setting flag. In case of a random crash like this, I wouldn’t be surprised if disabling Code stripping would fix this. If so, try to find the stripping level that still works.

hey, you, yeah you, you from the future.
we solved it by switching to dedicated server builds