Skip to content
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

If the server is started via Systemd, then it will not start when rebooting via RCON. #279

Open
Timofei302 opened this issue Oct 17, 2023 · 10 comments

Comments

@Timofei302
Copy link

Systemd service config:
Screenshot_20231017_190858

@geneotech
Copy link
Member

geneotech commented Oct 17, 2023

I see. I haven't really designed it yet to be run as a service, will have to look into it later. Would probably need a separate flag --as-service and have a separate restart logic for it. Do you think a service can update and restart itself though? Especially with additional flags?

@geneotech
Copy link
Member

Actually wouldn't it be enough for the game to return 1; since you've set Restart=on-failure?

@Timofei302
Copy link
Author

Actually wouldn't it be enough for the game to return 1; since you've set Restart=on-failure?

Logically, this should be enough, but I think it's worth doing research first by making a script that will return exit code 1 and see how systemd behaves.

@geneotech
Copy link
Member

geneotech commented Oct 17, 2023

Hey, I think your server keeps restarting or perhaps has a high send_heartbeat_to_server_list_once_every_secs set (I should probably clamp the value automatically), because the server list detects it as a new server once every few minutes, and it keeps spamming new server notifications :) The timeout for a server to be removed from the server list is 60 seconds.

@Timofei302
Copy link
Author

Hey, I think your server keeps restarting or perhaps has a high send_heartbeat_to_server_list_once_every_secs set (I should probably clamp the value automatically), because the server list detects it as a new server once every few minutes, and it keeps spamming new server notifications :) The timeout for a server to be removed from the server list is 60 seconds.

idk what caused this, since everything is fine with my settings (at least everything was fine), and I am not reconfiguring the server now (so that when I configure the server, I often reboot hypersomnia via systemctl).

Screenshot_20231017-212317.jpg

@Timofei302
Copy link
Author

Screenshot_20231017-213115.jpg

@geneotech
Copy link
Member

geneotech commented Oct 17, 2023

It seems the problem is fixed, it now sends the heartbeats correctly 👍

@Timofei302
Copy link
Author

The server still goes missing every 5 minutes :/

@geneotech
Copy link
Member

Yeah, just noticed, not sure what could be the cause, perhaps packet loss? What if you set send_heartbeat_to_server_list_once_every_secs to e.g. 3?

@Timofei302
Copy link
Author

Yeah, just noticed, not sure what could be the cause, perhaps packet loss? What if you set send_heartbeat_to_server_list_once_every_secs to e.g. 3?

Hmm. By default, my server is already configured to send a "heartbeat" every 10 seconds.
Screenshot_20231017-220755.jpg

Therefore, there are two possible reasons - my hosting provider is still under ddos attack and this has started to negatively affect the operation of my vds, or someone or something is trying to break the connection of my vds with your master server on your side.

I can't think of any other assumptions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants