[GH-ISSUE #1752] Backup lock file included in backup #1367

New issue

Closed

opened 2026-02-27 02:56:43 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 02:56:43 +03:00

Owner

Originally created by @ghost on GitHub (Dec 27, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1752

Issue:
When restoring a backup created with the (in this case) ./rustserver backup command, it also backs up the .backup.lock file located in /home/user/lgsm/tmp. After restoring the backup this causes issues when running a new backup task is started, as the lock file causes the system to believe a backup is already running.

Possible Solution:
If possible this could be solved by skipping the .lock.backup file when making a backup.

Originally created by @ghost on GitHub (Dec 27, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1752 **Issue:** When restoring a backup created with the (in this case) ./rustserver backup command, it also backs up the .backup.lock file located in /home/user/lgsm/tmp. After restoring the backup this causes issues when running a new backup task is started, as the lock file causes the system to believe a backup is already running. **Possible Solution:** If possible this could be solved by skipping the .lock.backup file when making a backup.

kerem

2026-02-27 02:56:43 +03:00

closed this issue
added the
type: bug
label

kerem commented

2026-02-27 02:56:43 +03:00

Author

Owner

@ghost commented on GitHub (Dec 27, 2017):

I've just located the following line in fn_backup_compression(): rm -f "${tmpdir}/.backup.lock"

For some reason this does not seem to happen when compressing the backup.

@ghost commented on GitHub (Dec 27, 2017): I've just located the following line in fn_backup_compression(): rm -f "${tmpdir}/.backup.lock" For some reason this does not seem to happen when compressing the backup.

kerem commented

2026-02-27 02:56:43 +03:00

Author

Owner

@UltimateByte commented on GitHub (Dec 27, 2017):

Hello,
Thanks for reporting.
I would rather solve this by excluding the tmpdir since it's useless to backup it anyways.

PS: The given command happens after the compression is complete which is why it compresses the lock file into the backup.

@UltimateByte commented on GitHub (Dec 27, 2017): Hello, Thanks for reporting. I would rather solve this by excluding the tmpdir since it's useless to backup it anyways. PS: The given command happens after the compression is complete which is why it compresses the lock file into the backup.

kerem commented

2026-02-27 02:56:43 +03:00

Author

Owner

@lock[bot] commented on GitHub (Mar 12, 2019):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Mar 12, 2019): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.