-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
When starting from systemd in server mode, the processor loads 100% #4299
Comments
try use the server creation shell script in tools or gnu scrern / tmux |
@Benau do you mean add |
@Benau Thank you! It's works! |
Any reason it would use 5% continuously in idle? I have a bunch of other services and they stay at 0% if no activity. Debian Buster, arm64, RPi3+, build from git SERVER_ONLY. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When I run the command
/opt/stk/bin/supertuxkart --server-config=/home/stk/stk/server.xml
from the stk user, all ok.I want to make the stk server available while my vps is on. I make systemd service.
When I staring the systemd service, My server is available in game, but the vps CPU is loaded at 99-100%.
Steps to reproduce
When I run the command
/opt/stk/bin/supertuxkart --server-config=/home/stk/stk/server.xml
from the stk user, everything is fine. I see a log in the console.My server appears in the list of private servers. I can connect and play. The processor is loaded at 5%.
Now I want to make the stk server available while my vps is on.
I create user
stk
and systemd service/etc/systemd/system/stk.service
:I run service.
journalctl -u stk.service -f
command output shows:My server appears in the list of private servers. I can connect and play (with lags). The processor is loaded at 99-100%.
The log is only updated when I stop the service
systemctl stop stk.service
Configuration
STK release version:
1.1
STK Source (PPA, distribution package, official binary, etc.): branch
1.1
of github. compiled withcmake
and-DSERVER_ONLY=ON
option.System: Debian stretch
Graphics card: unknown
CPU:
Gamepads/keyboards models if related to the issue:
none
The text was updated successfully, but these errors were encountered: