-
-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bad PID #1239
Comments
Unfortunately there's not much to go on to say why the game server is exiting after 5 seconds. |
We are using Debian 11 |
It sounds like there is still potentially something wrong with the ARK server install. Please try running |
Could it be that the error is caused by the presence of Cyrillic symbols in path? |
Yes, it is quite possible that the ARK / Unreal Engine 4 server does not properly handle paths with characters that have the high bit set (as is the case with UTF-8, KOI8, or ISO-8859-5 encoded Cyrillic characters). We know it doesn't handle characters with the high bit set on the command-line or in its config file (where it only understands either 7-bit ASCII or 16-bit UTF-16). Edit: Indeed, UE-22616 mentions this, and was closed as "By Design". I think you might need to move the game server to a path that does not have characters outside 7-bit ASCII. |
Getting error when trying to start server
steam@server-main:~$ arkmanager run
Running command 'run' for instance 'main'
2022-12-20 01:16:39: start
2022-12-20 01:16:39: Running /media/user/Файлопом/user/ARK/ShooterGame/Binaries/Linux/ShooterGameServer TheIsland?RCONEnabled=True?RCONPort=32330?SessionName=ARK\ Server\ Tools?Port=7778?QueryPort=27015?ServerPassword?ServerAdminPassword=keyboardcat?MaxPlayers=70?ServerPassword?listen
2022-12-20 01:16:39: Server PID: 15257
Shutdown handler: initalize.
Using binned.
4.5.1-0+UE4 7038 3077 404 10
/usr/local/bin/arkmanager: line 1314: 15257 Emergency stop "$arkserverroot/$arkserverexec" "$arkserveropts" "${arkextraopts[@]}"
2022-12-20 01:16:44: Bad PID ''; expected '15257'
2022-12-20 01:16:44: exited with status 0
The text was updated successfully, but these errors were encountered: