Update state (0x3) reconfiguring, progress: 0.00 (0 / 0) Loading Steam API.Warning: failed to init SDL thread priority manager: SDL not = "1"Ĭonnecting anonymously to Steam Public.Logged in OK Steam Console Client (c) Valve Corporation Redirecting stderr to '/home/steam/.steam/logs/stderr.txt' Sed: can't read /ark/server/steamapps/appmanifest_376030.acf: No such file or directoryĬp: cannot stat '/ark/server/Engine/.': No such file or directoryĬp: cannot stat '/ark/server/linu圆4/.': No such file or directoryĬp: cannot stat '/ark/server/ShooterGame/Content/Mods/111111111/.': No such file or directoryĬp: cannot stat '/ark/server/ShooterGame/Content/Mods/111111111.mod': No such file or directoryĬp: cannot stat '/ark/server/steamapps/.': No such file or directoryĭownloading ARK updateExecuting /home/steam/.steam/steamcmd/steamcmd.sh 1 +login anonymous +force_install_dir /ark/staging +app_update 376030 +quit Your ARK server exec could not be found. Running command 'start' for instance 'main' Starting periodic command scheduler cron.For this you will need your ServerAdminPassword and you'll have to enter the following cheat commands: (they are admin commands, but they call them cheat commands.# Ark Server - Sat Jun 20 20:47:Ĭleaning up any leftover arkmanager files.Ĭreating arkmanager.cfg from environment variables. Save yourself endless misery with the following in game commands to force the server to save. Also be aware that the server now autosaves every 15 minutes. The previous issues with linux autosaving on exit seem to have been corrected. They have been making massive improvements in the boot speed of the server, so it should be up much faster. Do keep in mind that right now I've seen this server take over 20 minutes to be up and responding. Look for ShooterGameServer and if it's eating 3+ GB ofRAM, then it should be up and running. In Ubuntu you'll want to open the System Monitor. I know how that sounds, but right now that is just where it is at. For now the only way to really tell if the server is up and running, other than logging in with the game client, is to look at system performance and the memory used by the server. However, even with that error on the screen, if your file limits are set right, and your ports are open, you should be good to go. Remember, right now it's an Alpha Early Access release. At this time the error can be cause by the file limit being too low, or the fact that it shouldn't even be making that call in the first place. First, you haven't setup the open file limit properly. This is about all you will ever see in this console for now.
0 kommentar(er)
