Description
After executing /autoserver reload, the plugin loses server-specific configurations (specifically stop-command), causing an infinite loop of failed stop attempts that spams the console with RuntimeException: Command not found errors.
| Item |
Version/Details |
| Proxy Software |
Velocity |
| Plugin |
AutoServer |
| Related Software |
MCSManager Panel (daemon API) |
Steps to Reproduce
- Configure a server (e.g., warwall) with stop-command in config.yml
- Start the Velocity proxy with AutoServer loaded
- Execute
/autoserver reload in console
- Wait for the auto-shutdown timer to trigger (or trigger it manually)
- Observe console spam with Stop command not found for warwall
Expected Behavior
/autoserver reload should reload configuration without losing existing server definitions
If a server configuration is invalid, the plugin should log a single warning and skip that server
Failed stop attempts should not retry in a tight loop
Actual Behavior
[10:55:20 INFO] [autoserver]: Configuration reloaded.
[10:56:35 ERROR] [autoserver]: Stop command not found for warwall
[10:56:35 ERROR] [autoserver]: Failed to stop server: java.lang.RuntimeException: Command not found
[10:56:35 ERROR] [autoserver]: error: java.lang.RuntimeException: Command not found
[10:56:35 INFO] [autoserver]: Attempting to stop server: warwall
[10:56:35 ERROR] [autoserver]: Stop command not found for warwall
... (repeats 20+ times per second)
Logs
Before reload (working):
[10:39:16 INFO] [autoserver]: Running start command for warwall server. "curl -s -X GET 'http://localhost:18700/api/protected_instance/open?daemonId=...'"
[10:39:34 INFO] [autoserver]: Server warwall is online. Moving queued players...
After reload (broken):
[10:56:35 ERROR] [autoserver]: Stop command not found for warwall
[10:56:35 ERROR] [autoserver]: Failed to stop server: java.lang.RuntimeException: Command not found
[10:56:36 INFO] [autoserver]: Attempting to stop server: warwall
... (infinite loop)
Impact
latest.log
Console spam: ~20+ error messages per second
CPU usage: Wasted cycles on failed retry loop
Operational risk: Unable to gracefully stop servers after config reload
Data integrity: Potential race conditions if stop commands are intermittently missing
By the way, when setting autoShutdownDelay = 0 (intending to disable auto-shutdown), the plugin still attempts to stop servers after /autoserver reload.
Description
After executing /autoserver reload, the plugin loses server-specific configurations (specifically stop-command), causing an infinite loop of failed stop attempts that spams the console with RuntimeException: Command not found errors.
Steps to Reproduce
/autoserver reloadin consoleExpected Behavior
/autoserver reloadshould reload configuration without losing existing server definitionsIf a server configuration is invalid, the plugin should log a single warning and skip that server
Failed stop attempts should not retry in a tight loop
Actual Behavior
Logs
Before reload (working):
After reload (broken):
Impact
latest.log
Console spam: ~20+ error messages per second
CPU usage: Wasted cycles on failed retry loop
Operational risk: Unable to gracefully stop servers after config reload
Data integrity: Potential race conditions if stop commands are intermittently missing
By the way, when setting autoShutdownDelay = 0 (intending to disable auto-shutdown), the plugin still attempts to stop servers after /autoserver reload.