starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #3307] Details Command Not Showing Accurate Backups Information #2287

New issue

Closed

opened 2026-02-27 03:02:00 +03:00 by kerem · 5 comments

kerem commented

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

Owner

Originally created by @PoppaShell on GitHub (Feb 26, 2021).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3307

User Story

When using the Details command, it gives a Section of Information titled "Backups". Under this Section, I am seeing inaccurate information for "Latest Backup" as far as the date and file specified.

Basic info

Distro: [Ubuntu 20.04.2 LTS]
Game: [Valheim]
Command: [Details]
LinuxGSM version: [v21.1.3]

Further Information

As can be seen in my attached screenshot, it shows the following:

Backups

No. of backups: 4
Latest backup:
date: Thu 25 Feb 2021 04:04:07 PM UTC (1 day ago)
file: /home/vhserver/lgsm/backup/vhserver-2021-02-25-160202.tar.gz
size: 785M

But if you look at the output from an LS on the backups directory, you can see the following backups, which is more recent than what shows above.

vhserver-2021-02-25-160202.tar.gz
vhserver-2021-02-26-000201.tar.gz
vhserver-2021-02-26-080202.tar.gz
vhserver-2021-02-26-160201.tar.gz

To Reproduce

Steps to reproduce the behaviour:

Run "./vhserver details" from the game server directory
Observe the "Latest backup" date & file details under the "Backups" section
Run "ls /home/vhserver/lgsm/backup/"
Compare the latest backup file from the ls output and compare to the "Latest backup" information from the details command output

Expected behaviour

The expected behaviour is for the "Latest backup" information from the details command to be accurate.

Screenshot(s)

Originally created by @PoppaShell on GitHub (Feb 26, 2021). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3307 ## User Story When using the Details command, it gives a Section of Information titled "Backups". Under this Section, I am seeing inaccurate information for "Latest Backup" as far as the date and file specified. ## Basic info * **Distro:** [Ubuntu 20.04.2 LTS] * **Game:** [Valheim] * **Command:** [Details] * **LinuxGSM version:** [v21.1.3] ## Further Information As can be seen in my attached screenshot, it shows the following: Backups ================================= No. of backups: 4 Latest backup: date: Thu 25 Feb 2021 04:04:07 PM UTC (1 day ago) file: /home/vhserver/lgsm/backup/vhserver-2021-02-25-160202.tar.gz size: 785M But if you look at the output from an LS on the backups directory, you can see the following backups, which is more recent than what shows above. vhserver-2021-02-25-160202.tar.gz vhserver-2021-02-26-000201.tar.gz vhserver-2021-02-26-080202.tar.gz vhserver-2021-02-26-160201.tar.gz ## To Reproduce Steps to reproduce the behaviour: 1. Run "./vhserver details" from the game server directory 2. Observe the "Latest backup" date & file details under the "Backups" section 3. Run "ls /home/vhserver/lgsm/backup/" 4. Compare the latest backup file from the ls output and compare to the "Latest backup" information from the details command output ## Expected behaviour The expected behaviour is for the "Latest backup" information from the details command to be accurate. ## Screenshot(s) ![image](https://user-images.githubusercontent.com/29165443/109344892-f8a30d80-7834-11eb-88ea-966ec3500a8a.png)

kerem

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

closed this issue
added the
type: bug

command: backup

distro: Ubuntu
labels

kerem commented

2026-02-27 03:02:01 +03:00

Author

Owner

@nicholas-weidmann commented on GitHub (Feb 26, 2021):

Can confirm this behavior. I sat up a cronjob yesterday and just noticed, when checking it today, that the Backup shown as latest, has the wrong timestamp.

Distro: Ubuntu 18.04.4 LTS
Game: Valheim
LinuxGSM Version: v21.1.3

@nicholas-weidmann commented on GitHub (Feb 26, 2021): Can confirm this behavior. I sat up a cronjob yesterday and just noticed, when checking it today, that the Backup shown as latest, has the wrong timestamp. Distro: Ubuntu 18.04.4 LTS Game: Valheim LinuxGSM Version: v21.1.3 ![image](https://user-images.githubusercontent.com/18269098/109362284-fec3d900-788a-11eb-915b-e896fc5853d2.png)

kerem commented

2026-02-27 03:02:01 +03:00

Author

Owner

@nbgibson commented on GitHub (Mar 1, 2021):

To chime in, this isn't limited to the details command as the backup command appears to use the same logic.

It appears the date logic implementation might be assuming a hard coded 31 day month in its calculations. My reasoning being that a backup run today (3/1) shows the most recent previous backup (2/28) as being from 3 days prior. Also note that subsequent backups for today show the previous backup as being from the day before; despite said backup being from about 15 seconds ago, so something in the diff calculation is a bit funky.

@nbgibson commented on GitHub (Mar 1, 2021): To chime in, this isn't limited to the details command as the backup command appears to use the same logic. It appears the date logic implementation might be assuming a hard coded 31 day month in its calculations. My reasoning being that a backup run today (3/1) shows the most recent previous backup (2/28) as being from 3 days prior. Also note that subsequent backups for today show the previous backup as being from the day before; despite said backup being from about 15 seconds ago, so something in the diff calculation is a bit funky.

kerem commented

2026-02-27 03:02:01 +03:00

Author

Owner

@Xalorous commented on GitHub (Mar 3, 2021):

Confirm. I also see this behavior.

Server: Centos 7.9
Script name: vhserver
LinuxGSM version: v21.1.3

@Xalorous commented on GitHub (Mar 3, 2021): Confirm. I also see this behavior. Server: Centos 7.9 Script name: vhserver LinuxGSM version: v21.1.3

kerem commented

2026-02-27 03:02:01 +03:00

Author

Owner

@h3o66 commented on GitHub (Mar 7, 2021):

This should be fine with the next release, as already noted in #3339
This regressed in #3328 on the develop branch and should be fixed by #3348 in the end

@h3o66 commented on GitHub (Mar 7, 2021): This should be fine with the next release, as already noted in #3339 This regressed in #3328 on the develop branch and should be fixed by #3348 in the end

kerem commented

2026-02-27 03:02:01 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 15, 2022):

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

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

kerem referenced this issue

2026-02-27 03:55:00 +03:00

[PR #2287] [MERGED] Add minecraft test to travis #3571