feat: improve upgrade process with lock file and background execution #346
+53
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update ensures that the upgrade process completes reliably, even if the SSH connection drops, fully resolving the original issue.
Key Features:
-Resilience to SSH Disconnections: The upgrade runs under nohup in the background, allowing it to continue seamlessly after an SSH disconnect.
-Concurrent Execution Prevention: The lock file mechanism ensures that only one upgrade process can run at a time.
-Monitoring Support: Users can track progress using:
tail -f /var/log/hysteria_upgrade.log-Status Verification: Users can check whether the upgrade is still active with:
ps aux | grep upgrade.sh-Recovery From Interruptions: The system detects interrupted upgrades and handles them safely.
-Updated User Experience
When selecting option 3 — Update Panel, users now receive:
-A message indicating that the upgrade is running in the background
-The PID of the running upgrade process
-Instructions for monitoring and checking status
-Confirmation that they may safely disconnect their SSH session
These enhancements are not yet tested and require verification before production use.