starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-26 06:35:54 +03:00

[GH-ISSUE #815] Arma 3 Server segfaults on start-up #657

New issue

Closed

opened 2026-02-27 02:02:56 +03:00 by kerem · 7 comments

kerem commented

2026-02-27 02:02:56 +03:00

Owner

Originally created by @dr-waterstorm on GitHub (May 16, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/815

Originally assigned to: @dgibbs64 on GitHub.

Hi,

first I wanted to thank you for your effort in creating all those game-server managers :-)

Regarding my found "bug": I just wanted to install an Arma 3 Server on my Linux dedicated machine and it segfaulted on startup. It took me some time to figure out what happened and I have to say the good old segfault is not very meaningful.

The problem is:
You have a script called "fix_arma.sh", which creates an Arma 3 profile folder in {$rootdir}/.local/share/. However here are multiple issues here, first your script creates (at least on ubuntu 14.04) a folder called "Arma\ 3" instead of "Arma 3" and second Arma needs to have an additional folder called "Arma 3 - Other Profiles" and third Arma needs to have those folder in the home dir of the user running the game server instead of the root of the gameserver itself.

So the command creating those folders should be:

mkdir -p ~/".local/share/Arma 3" && mkdir -p ~/".local/share/Arma 3 - Other Profiles"

This created the Arma 3 folders in my home dir and everything started to work.

It would be nice if you can fix your script to make the game server manager work right out of the box again.

I hope this will help other people trying to use the gameservermanager on Linux :). And thanks again for your efforts!!

Originally created by @dr-waterstorm on GitHub (May 16, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/815 Originally assigned to: @dgibbs64 on GitHub. Hi, first I wanted to thank you for your effort in creating all those game-server managers :-) Regarding my found "bug": I just wanted to install an Arma 3 Server on my Linux dedicated machine and it segfaulted on startup. It took me some time to figure out what happened and I have to say the good old segfault is not very meaningful. The problem is: You have a script called "fix_arma.sh", which creates an Arma 3 profile folder in {$rootdir}/.local/share/. However here are multiple issues here, first your script creates (at least on ubuntu 14.04) a folder called "Arma\ 3" instead of "Arma 3" and second Arma needs to have an additional folder called "Arma 3 - Other Profiles" and third Arma needs to have those folder in the home dir of the user running the game server instead of the root of the gameserver itself. So the command creating those folders should be: `mkdir -p ~/".local/share/Arma 3" && mkdir -p ~/".local/share/Arma 3 - Other Profiles"` This created the Arma 3 folders in my home dir and everything started to work. It would be nice if you can fix your script to make the game server manager work right out of the box again. I hope this will help other people trying to use the gameservermanager on Linux :). And thanks again for your efforts!!

kerem

2026-02-27 02:02:56 +03:00

closed this issue
added the
game: ARMA 3
label

kerem commented

2026-02-27 02:02:56 +03:00

Author

Owner

@dgibbs64 commented on GitHub (May 16, 2016):

Should be easy to resolve. I will fix on the development branch as it will be released soon

@dgibbs64 commented on GitHub (May 16, 2016): Should be easy to resolve. I will fix on the development branch as it will be released soon

kerem commented

2026-02-27 02:02:57 +03:00

Author

Owner

@igeighty commented on GitHub (May 23, 2016):

Thanks Daniel. it took me a while to track where that "Arma\ 3" folder was coming from :)

@igeighty commented on GitHub (May 23, 2016): Thanks Daniel. it took me a while to track where that "Arma\ 3" folder was coming from :)

kerem commented

2026-02-27 02:02:57 +03:00

Author

Owner

@UltimateByte commented on GitHub (May 23, 2016):

@dgibbs64 So was it released with the last major update ?

@UltimateByte commented on GitHub (May 23, 2016): @dgibbs64 So was it released with the last major update ?

kerem commented

2026-02-27 02:02:57 +03:00

Author

Owner

@igeighty commented on GitHub (May 23, 2016):

i just did a reinstall using the arma3server script, and the folder .local/share/Arma\ 3/ is still present.

on the first run of the server is did create the required folders..
/.local/share/Arma 3
/.local/share/Arma 3 - Other Profiles

i did not have to create these manually using
mkdir -p ~/".local/share/Arma 3" && mkdir -p ~/".local/share/Arma 3 - Other Profiles"
the server had created a default player.armaprofile when was initially run in the folder
.local/share/Arma 3 - Other Profiles/Player/player.armaprofile this default profile does not contain many variables, and needs to be edited manually to suit the individual server.

I then went through and edited the default to contain a more detailed profile containing settings for the difficulty and other parameters. from this example https://community.bistudio.com/wiki/server.armaprofile#Linux

As far as i can see the .armaprofile file is created by default in
.local/share/Arma 3 - Other Profiles/Player/
on initial startup when no -NAME value is specified in the startup parameters.

This default player.armaprofile is being created when using ./arma3server start as there is none specified in the parms value in the arma3server script ?
parms="-netlog -ip=${ip} -port=${port} -cfg=${networkcfgfullpath} -config=${servercfgfullpath} -mod=${mods} -servermod=${servermods} -bepath=${bepath} -autoinit -loadmissiontomemory"

this default .profile is still being loaded by the server on startup, which is the same behaviour when running the server executable without any parameters manually.

i am sorry if i am not explaining it properly, i am more a point to a diagram guy than a wordsmith :)

cheers for your ongoing work guys.
please feel free to contact me if you need testing done,

@igeighty commented on GitHub (May 23, 2016): i just did a reinstall using the arma3server script, and the folder `.local/share/Arma\ 3/` is still present. on the first run of the server is did create the required folders.. `/.local/share/Arma 3` `/.local/share/Arma 3 - Other Profiles` i did not have to create these manually using `mkdir -p ~/".local/share/Arma 3" && mkdir -p ~/".local/share/Arma 3 - Other Profiles"` the server had created a default player.armaprofile when was initially run in the folder `.local/share/Arma 3 - Other Profiles/Player/player.armaprofile` this default profile does not contain many variables, and needs to be edited manually to suit the individual server. I then went through and edited the default to contain a more detailed profile containing settings for the difficulty and other parameters. from this example https://community.bistudio.com/wiki/server.armaprofile#Linux As far as i can see the .armaprofile file is created by default in `.local/share/Arma 3 - Other Profiles/Player/` on initial startup when no `-NAME` value is specified in the startup parameters. This default player.armaprofile is being created when using `./arma3server start` as there is none specified in the parms value in the arma3server script ? `parms="-netlog -ip=${ip} -port=${port} -cfg=${networkcfgfullpath} -config=${servercfgfullpath} -mod=${mods} -servermod=${servermods} -bepath=${bepath} -autoinit -loadmissiontomemory"` this default .profile is still being loaded by the server on startup, which is the same behaviour when running the server executable without any parameters manually. i am sorry if i am not explaining it properly, i am more a point to a diagram guy than a wordsmith :) cheers for your ongoing work guys. please feel free to contact me if you need testing done,

kerem commented

2026-02-27 02:02:57 +03:00

Author

Owner

@dgibbs64 commented on GitHub (May 24, 2016):

I have hopefully made the required changes. Please let me know if this does what is required or anymore changes are needed

@dgibbs64 commented on GitHub (May 24, 2016): I have hopefully made the required changes. Please let me know if this does what is required or anymore changes are needed

kerem commented

2026-02-27 02:02:57 +03:00

Author

Owner

@igeighty commented on GitHub (May 25, 2016):

Thanks Daniel, the new script does no longer creates the .local/share/Arma\ 3/directory.

it does create the correct
/.local/share/Arma 3
and
/.local/share/Arma 3 - Other Profiles

Now i just have to get my head around the -name parameter in the arma server startup line which the specifies which *.Arma3Profile to use, and see how this can be incorporated into your script to get the correct .Arma3Profile file to load.

the other main stumbling block is the documentation from bohemia on these linux servers :)

i have install github onto my mac at home, and will try and contribute as best as i can.

thanks again, ill keep hunting the gremlins :)

@igeighty commented on GitHub (May 25, 2016): Thanks Daniel, the new script does no longer creates the `.local/share/Arma\ 3/`directory. it does create the correct `/.local/share/Arma 3` and `/.local/share/Arma 3 - Other Profiles` Now i just have to get my head around the -name parameter in the arma server startup line which the specifies which *.Arma3Profile to use, and see how this can be incorporated into your script to get the correct .Arma3Profile file to load. the other main stumbling block is the documentation from bohemia on these linux servers :) i have install github onto my mac at home, and will try and contribute as best as i can. thanks again, ill keep hunting the gremlins :)

kerem commented

2026-02-27 02:02:57 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Jul 19, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.