starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-27 07:05:58 +03:00

[GH-ISSUE #414] Update on start New Feature doesnt work on Latest TF2 update #336

New issue

Closed

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

kerem commented

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

Owner

Originally created by @medic917 on GitHub (Jun 3, 2015).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/414

Anyone else try the new script with the updateonstart="yes" option?
I configured it and it does check for updates on start, but it gives false information and says it doesn't need updates when it does.

Found out on my first TF2 update for my TF2 servers using this new feature.

Originally created by @medic917 on GitHub (Jun 3, 2015). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/414 Anyone else try the new script with the updateonstart="yes" option? I configured it and it does check for updates on start, but it gives false information and says it doesn't need updates when it does. Found out on my first TF2 update for my TF2 servers using this new feature.

kerem

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

closed this issue
added the
type: bug

type: feature
labels

kerem commented

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

Author

Owner

@medic917 commented on GitHub (Jun 3, 2015):

Here is a screen shot. It seems like the database it uses is outdated or slow on updates.
http://i.snag.gy/LlWX6.jpg

Note this is when using ./tf2server update rather than the start. With just ./tf2server start, it gives that it is updated when it is not.

@medic917 commented on GitHub (Jun 3, 2015): Here is a screen shot. It seems like the database it uses is outdated or slow on updates. http://i.snag.gy/LlWX6.jpg Note this is when using ./tf2server update rather than the start. With just ./tf2server start, it gives that it is updated when it is not.

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Jun 3, 2015):

Damn it wrong issue. I meant fixed issue #413

@dgibbs64 commented on GitHub (Jun 3, 2015): Damn it wrong issue. I meant fixed issue #413

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Jun 3, 2015):

This isn't an issue as such in that you do get the latest update.

What happens is that the script found a restart request in the logs and applies the update. The script then continues to use SteamCMD to check for updates...by this time the server has just updated so the SteamCMD check states there is no update which is now true as it just updated.

I will make alterations so make this less confusing on the front end :)

@dgibbs64 commented on GitHub (Jun 3, 2015): This isn't an issue as such in that you do get the latest update. What happens is that the script found a restart request in the logs and applies the update. The script then continues to use SteamCMD to check for updates...by this time the server has just updated so the SteamCMD check states there is no update which is now true as it just updated. I will make alterations so make this less confusing on the front end :)

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Jun 3, 2015):

Fixed related issue I found github.com/dgibbs64/linuxgsm@4a5e4cffb6

@dgibbs64 commented on GitHub (Jun 3, 2015): Fixed related issue I found https://github.com/dgibbs64/linuxgsm/commit/4a5e4cffb64d56e15a69e63d1642f37158559050

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Oct 26, 2015):

This should fix the issue github.com/dgibbs64/linuxgsm@d69b8672c6

@dgibbs64 commented on GitHub (Oct 26, 2015): This should fix the issue https://github.com/dgibbs64/linuxgsm/commit/d69b8672c6990dd366413ee708fae3b2a6414a07

kerem commented

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

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

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 (Jul 19, 2018): 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.