OS Name/Version: Proxmox (AMP installed on Debian 13 LXC)
Product Name/Version: AMP v2.7.2.8 (Build: 20260520.1)
Problem Description:
When my server resets and backs up nightly, it restarts successfully and the container also restarts successfully. I am able to access AMP’s browser panel immediately. I have the following configurations set:
- Main Panel → Configuration → Instance Deployment → Instance Management
- Both “Autostart Instances” and “Automatically Reactivate Instances” are turned on
- Instance #1 (Vintage Story) → Configuration → System Settings → System
- “Startup Mode” is set to Start
- Instance #2 (Vintage Story) → Configuration → System Settings → System
- “Startup Mode” is set to Start
- Instance #3 (Runescape Dragonwilds) → Configuration → System Settings → System
- “Startup Mode” is set to Start
All three Instances have the same exact configurations. What I keep running into is that only Instance #3 is starting on boot. #1 and #2 remain stopped/shutdown. I haven’t seen any errors in the Deployment Log - actually when I check the deployment log after reboot I don’t see any notes at all for that matter. Both #1 and #2 need to be started manually. They start just fine and run without issue, though I did note they sometimes take more than 10-15 seconds to start up. They simply won’t survive a machine restart.
Steps to reproduce:
- Scheduled server machine reboot & backup takes place
- Machine reboots
- AMP reboots
- Instances attempt to reboot
- All but #3 instance fail to reboot
Actions taken to resolve so far:
- Tried turning configuration settings on and off
- Tried extending “Instance Start Delay” from 10,000 to 20,000ms
- Tried manually rebooting the server machine instead of on schedule (same problem occurs)
Is it possible the startup of the instances is taking longer than the Instance Start Delay can manage and they’re somehow getting hung up trying to start both at once? But if that was the case, why wouldn’t #3 also be affected?