Ardamay Posted December 16, 2024 Report Posted December 16, 2024 (edited) Hi, I'm running my server on Ubuntu 24.04.1 using server.sh in terminal. I noticed in my logs that im getting the warning " [Server Warning] Server overloaded. A Tick took 1122ms to complete. ", where can I look to see what is causing this? Also is this normal? the server runs fine, it hasn't crashed, and I've not noticed any lag spikes. Edited December 16, 2024 by Ardamay 1
Absolute Lambda Posted December 25, 2024 Report Posted December 25, 2024 I see it a lot in servers so personally I wouldn't stress over it. 1
Voldemort Posted January 12, 2025 Report Posted January 12, 2025 (edited) On 12/25/2024 at 11:56 PM, Absolute Lambda said: I see it a lot in servers so personally I wouldn't stress over it. yea getting same thing Vintage Story [Server Warning] Server overloaded. A tick took 1295ms to complete. wonder why it is spamming every 10min Edited January 13, 2025 by Adnyeus
Thorfinn Posted January 13, 2025 Report Posted January 13, 2025 (edited) IME, that's usually someone running with too high of a view distance for his machine, and mapgen can't keep up. Whether or not you want to worry about it is up to you. The game is fairly fault tolerant -- if he stops running and finds something to do while his computer catches up, the problem usually resolves itself. But it is possible to get so far behind that the server crashes. [EDIT] If I'm interpreting what I'm seeing properly, the client is too busy generating blocks to receive from the server. That particular situation rarely happens in explored territory, unless someone has a really outdated machine. Edited January 13, 2025 by Thorfinn 1
Voldemort Posted January 13, 2025 Report Posted January 13, 2025 (edited) 53 minutes ago, Thorfinn said: IME, that's usually someone running with too high of a view distance for his machine, and mapgen can't keep up. Whether or not you want to worry about it is up to you. The game is fairly fault tolerant -- if he stops running and finds something to do while his computer catches up, the problem usually resolves itself. But it is possible to get so far behind that the server crashes. [EDIT] If I'm interpreting what I'm seeing properly, the client is too busy generating blocks to receive from the server. That particular situation rarely happens in explored territory, unless someone has a really outdated machine. I asked other server owners, and they are getting warnings of 3000ms to 6000ms, and they say it's fine with no problems. They have modded servers with high populations. It's only a warning, but in reality, there's no overload. It would need to reach 23,000ms or 32,000ms, and over 60,000ms would cause a crash, according to what I've heard from others, though I'm not sure if that's accurate. I would love to setup custom automatic server restarts in config but im not sure where to look for it. Edited January 13, 2025 by Adnyeus
NoSleeves Posted January 27, 2025 Report Posted January 27, 2025 (edited) On 1/12/2025 at 7:53 PM, Adnyeus said: I asked other server owners, and they are getting warnings of 3000ms to 6000ms, and they say it's fine with no problems. They have modded servers with high populations. It's only a warning, but in reality, there's no overload. It would need to reach 23,000ms or 32,000ms, and over 60,000ms would cause a crash, according to what I've heard from others, though I'm not sure if that's accurate. I would love to setup custom automatic server restarts in config but im not sure where to look for it. You can set the Game Server up as a systemd service vim /etc/systemd/system/vintagestory.service You need to make sure that your WorkingDirectory and ExecStart paths are correct. I installed my game server in /opt/vintagestory/server, yours may be different Same with your User and Group [Unit] Description=Vintage Story Server Unit After=network.target [Service] WorkingDirectory=/opt/vintagestory/server ExecStart=dotnet VintagestoryServer.dll --dataPath /opt/vintagestory/data Restart=always RestartSec=30 StandardOutput=syslog StandardError=syslog SyslogIdentifier=VSSRV User=vintagestory Group=vintagestory [Install] WantedBy=multi-user.target systemctl daemon-reload systemctl start vintagestory.service systemctl enable vintagestory.service To see the logs you can either look at syslog or run: journalctl -u vintagestory.service -f This sets the game service to restart on every 30 seconds as long as the service is enables Edited January 27, 2025 by NoSleeves 1
Recommended Posts