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

Gmod Rcon breaks after 24-48 hours #1262

Open
3 tasks done
Midnight679 opened this issue Nov 30, 2024 · 0 comments
Open
3 tasks done

Gmod Rcon breaks after 24-48 hours #1262

Midnight679 opened this issue Nov 30, 2024 · 0 comments
Labels

Comments

@Midnight679
Copy link

Operating System

Ubuntu 22/04 lts

AMP Version and Build Date

2.6.0.6 - 20241120.1

AMP Release Stream

Mainline

I confirm that

  • I have searched for an existing bug report for this issue.
  • I am using the latest available version of AMP.
  • my operating system is up-to-date.

Intended Action

Start the server and have accurate state displayed, and a working console

Expected Behaviour

The state changes from starting to running once started, and the rcon to work

Actual Behaviour

The server is permanently in a starting state, and RCON does not work. Some times the instance logs show no error and say the command was sent to rcon but it does not actually send it. Most of the time, the following shows up in the logs. I am sure RCON is working on the actual gmod server side because I can RCON from inside the game, and via external rcon tools.

[18:52:05] [System:*** Warning/37] : Source RCON packet data empty. This typically means the server closed the connection.
11/30/2024 - 18:52:05: server_cvar: "sv_alltalk" "0"
[18:52:05] [RCON:*** Info/37] : Source RCON disconnecting...
[18:52:06] [RCON:*** Info/37] : Source RCON disconnected
[18:54:08] [Core:*** Activity/42] : Sent to console: say test

Reproduction

Create a new Gmod server and complete the basic configuration making sure to bind the server to same IP as the host machine. Leave the server running for 24-48 hours and restart the gmod server. Upon restart the behavior outlined above will be present

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

No branches or pull requests

1 participant