starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #1320] Teamspeak keeps updating Versions again #1021

New issue

Closed

opened 2026-02-27 02:54:53 +03:00 by kerem · 14 comments

kerem commented

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

Owner

Originally created by @J3n50m4t on GitHub (Feb 17, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1320

./ts3server update keeps updating version 3.0.12.4 amd64 to 3.0.13.6 amd64 everytime the script runs.

The server updates successfully, but the script always finds outdated versions

Originally created by @J3n50m4t on GitHub (Feb 17, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1320 `./ts3server update` keeps updating version `3.0.12.4 amd64 ` to `3.0.13.6 amd64` everytime the script runs. The server updates successfully, but the script always finds outdated versions ![image](https://cloud.githubusercontent.com/assets/13681191/23058598/0dc644d2-f4f6-11e6-8a61-93f55a915505.png)

kerem

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

closed this issue
added the
type: bug

cannot reproduce
labels

kerem commented

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

Author

Owner

@braunsonm commented on GitHub (Feb 17, 2017):

The script checks your console logs to find out your current version. Does this continue to happen after the server runs in normal operation for awhile?

@braunsonm commented on GitHub (Feb 17, 2017): The script checks your console logs to find out your current version. Does this continue to happen after the server runs in normal operation for awhile?

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Feb 17, 2017):

Also, the script checks current version from latest log, so if you changed your server time at some point, could explain the issue. Try clearing your ts3 logs, then restart the server, and try to update again.

@UltimateByte commented on GitHub (Feb 17, 2017): Also, the script checks current version from latest log, so if you changed your server time at some point, could explain the issue. Try clearing your ts3 logs, then restart the server, and try to update again.

kerem commented

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

Author

Owner

@J3n50m4t commented on GitHub (Feb 18, 2017):

The server keeped updating for 3 days with every from job.
I now cleared the logs. Will see if it updates tonight
Edit:
I cleared /home/ts3server/log /* restarted the server and it started updating again. Again 12.4

@J3n50m4t commented on GitHub (Feb 18, 2017): The server keeped updating for 3 days with every from job. I now cleared the logs. Will see if it updates tonight Edit: I cleared /home/ts3server/log /* restarted the server and it started updating again. Again 12.4

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Feb 18, 2017):

Go clear serverfiles/log. Actually what you cleared is only script logs, which are irrelevant to ts3server update.

Since i don't have the issue, must be something wrong on your side.

ts3terageek@webserver:~$ ./ts3server update
[  OK  ] Update ts3-server: Checking for update: teamspeak.com

No update available:
        Current version: 3.0.13.6
        Available version: 3.0.13.6

[  OK  ] Update ts3-server: No update available

Try this :

./ts3server stop
rm serverfiles/logs/*
./ts3server start
./ts3server update

Issue should be fixed

@UltimateByte commented on GitHub (Feb 18, 2017): Go clear serverfiles/log. Actually what you cleared is only script logs, which are irrelevant to ts3server update. Since i don't have the issue, must be something wrong on your side. ``` ts3terageek@webserver:~$ ./ts3server update [ OK ] Update ts3-server: Checking for update: teamspeak.com No update available: Current version: 3.0.13.6 Available version: 3.0.13.6 [ OK ] Update ts3-server: No update available ``` Try this : ```bash ./ts3server stop rm serverfiles/logs/* ./ts3server start ./ts3server update ``` Issue should be fixed

kerem commented

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

Author

Owner

@J3n50m4t commented on GitHub (Feb 18, 2017):

Didn't work as well.
I also tried to delete everything and started new install but I run into the same problem. Are there may any other logs?

ts3server@server:~$ ./ts3server stop
[  OK  ] Stopping ts3-server: TeamSpeak 3 Server
ts3server@server:~$ rm serverfiles/logs/*
ts3server@gspserver:~$ ./ts3server update
[  OK  ] Update ts3-server: Checking for update: teamspeak.com

Update available:
        Current build: 3.0.12.4 amd64
        Available build: 3.0.13.6 amd64


Applying update...
extracting teamspeak3-server_linux_amd64-3.0.13.6.tar.bz2...OK
copying to /home/ts3server/serverfiles...OK
[  OK  ] Starting ts3-server: TeamSpeak 3 Server
[  OK  ] Stopping ts3-server: TeamSpeak 3 Server
[  OK  ] Alert ts3-server: Sending Pushbullet alert

@J3n50m4t commented on GitHub (Feb 18, 2017): Didn't work as well. I also tried to delete everything and started new install but I run into the same problem. Are there may any other logs? ``` ts3server@server:~$ ./ts3server stop [ OK ] Stopping ts3-server: TeamSpeak 3 Server ts3server@server:~$ rm serverfiles/logs/* ts3server@gspserver:~$ ./ts3server update [ OK ] Update ts3-server: Checking for update: teamspeak.com Update available: Current build: 3.0.12.4 amd64 Available build: 3.0.13.6 amd64 Applying update... extracting teamspeak3-server_linux_amd64-3.0.13.6.tar.bz2...OK copying to /home/ts3server/serverfiles...OK [ OK ] Starting ts3-server: TeamSpeak 3 Server [ OK ] Stopping ts3-server: TeamSpeak 3 Server [ OK ] Alert ts3-server: Sending Pushbullet alert ```

kerem commented

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

Author

Owner

@J3n50m4t commented on GitHub (Feb 18, 2017):

After second update it works. Thanks @UltimateByte

@J3n50m4t commented on GitHub (Feb 18, 2017): After second update it works. Thanks @UltimateByte

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Feb 18, 2017):

/log not /logs

Edit: My bad, after double check you were right, it's "/logs"

@UltimateByte commented on GitHub (Feb 18, 2017): /log not /logs Edit: My bad, after double check you were right, it's "/logs"

kerem commented

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

Author

Owner

@JimTR commented on GitHub (Feb 18, 2017):

just a thought why would you need to do the above ? it looks like the script is not keeping up to date

@JimTR commented on GitHub (Feb 18, 2017): just a thought why would you need to do the above ? it looks like the script is not keeping up to date

kerem commented

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

Author

Owner

@J3n50m4t commented on GitHub (Feb 18, 2017):

I had a new fresh install with no changes at all (Ubuntu 16.04)
Updated successfully to latest version but the script wasn't able to check correctly
It works now, will have to wait for next update to check if it bugs again

@J3n50m4t commented on GitHub (Feb 18, 2017): I had a new fresh install with no changes at all (Ubuntu 16.04) Updated successfully to latest version but the script wasn't able to check correctly It works now, will have to wait for next update to check if it bugs again

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Feb 18, 2017):

Something went wrong on the machine that i can't figure out.
update_ts3.sh script finds latest logs by searching in ts3server*_0.log
Maybe for some reason your latest log was named ts3server*_1.log, and that's my only guess for now.

I can't either figure it out or reproduce with the few info that was given, and never had the issue even though i've been running several ts3servers using LGSM during the last years.

So unless something changes about this issue, the current status is:
cannot reproduce

@UltimateByte commented on GitHub (Feb 18, 2017): Something went wrong on the machine that i can't figure out. update_ts3.sh script finds latest logs by searching in ts3server*_0.log Maybe for some reason your latest log was named ts3server*_1.log, and that's my only guess for now. I can't either figure it out or reproduce with the few info that was given, and never had the issue even though i've been running several ts3servers using LGSM during the last years. So unless something changes about this issue, the current status is: `cannot reproduce`

kerem commented

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

Author

Owner

@J3n50m4t commented on GitHub (Feb 18, 2017):

I already have 2 logs with same stamp again
I can't provide more informations for now. Sorry

ts3server@server:~/serverfiles/logs$ ls
ts3server_2017-02-18__15_10_51.508109_0.log  ts3server_2017-02-18__15_10_51.508109_1.log

0.log

2017-02-18 15:10:51.508163|INFO    |ServerLibPriv |   |TeamSpeak 3 Server 3.0.13.6 (2016-11-08 08:48:33)
2017-02-18 15:10:51.508270|INFO    |ServerLibPriv |   |SystemInformation: Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 Binary: 64bit
2017-02-18 15:10:51.508306|INFO    |ServerLibPriv |   |Using hardware aes
2017-02-18 15:10:51.509119|INFO    |DatabaseQuery |   |dbPlugin name:    SQLite3 plugin, Version 3, (c)TeamSpeak Systems GmbH
2017-02-18 15:10:51.509166|INFO    |DatabaseQuery |   |dbPlugin version: 3.11.1
2017-02-18 15:10:51.509381|INFO    |DatabaseQuery |   |checking database integrity (may take a while)
2017-02-18 15:10:51.526117|WARNING |Accounting    |   |Unable to find valid license key, falling back to limited functionality
2017-02-18 15:10:52.017941|INFO    |              |   |Puzzle precompute time: 465
2017-02-18 15:10:52.018118|INFO    |FileManager   |   |listening on 0.0.0.0:30033, :::30033
2017-02-18 15:10:52.038274|INFO    |CIDRManager   |   |updated query_ip_whitelist ips: 127.0.0.1/32, ::1/128,

1.log

2017-02-18 15:10:52.038062|INFO    |VirtualServer |1  |listening on 0.0.0.0:9987, :::9987
2017-02-18 16:05:26.985979|INFO    |PktHandler    |1  |Dropping client 6 because of ping timeout 19 0 0
2017-02-18 17:57:35.961463|INFO    |PktHandler    |1  |Dropping client 8 because of ping timeout 19 0 0

kerem commented

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

Author

Owner

@cedarlug commented on GitHub (Feb 18, 2017):

I copied your ts3server....0.log file from your posting above and placed it locally.

When I parse your 0.log with the updatescript version snarf (line 51), it pulls out the correct value:

currentbuild=$(cat $(find ./* -name 'ts3server*_0.log' 2> /dev/null | sort | egrep -E -v '${rootdir}/.ts3version' | tail -1) | egrep -o 'TeamSpeak 3 Server ((\.)?[0-9]{1,3}){1,3}\.[0-9]{1,3}' | egrep -o '((\.)?[0-9]{1,3}){1,3}\.[0-9]{1,3}' | sort -V | tail -1)
gamer@cryptbookpro:/tmp$ echo $currentbuild
3.0.13.6

So --- You LIKELY have (had) another log file somewhere that's being pulled in.
What does just this yield:

find ./* -name 'ts3server*_0.log'

@cedarlug commented on GitHub (Feb 18, 2017): I copied your ts3server....0.log file from your posting above and placed it locally. When I parse your 0.log with the updatescript version snarf (line 51), it pulls out the correct value: ```bash currentbuild=$(cat $(find ./* -name 'ts3server*_0.log' 2> /dev/null | sort | egrep -E -v '${rootdir}/.ts3version' | tail -1) | egrep -o 'TeamSpeak 3 Server ((\.)?[0-9]{1,3}){1,3}\.[0-9]{1,3}' | egrep -o '((\.)?[0-9]{1,3}){1,3}\.[0-9]{1,3}' | sort -V | tail -1) gamer@cryptbookpro:/tmp$ echo $currentbuild 3.0.13.6 ``` So --- You LIKELY have (had) another log file somewhere that's being pulled in. What does just this yield: ```bash find ./* -name 'ts3server*_0.log' ```

kerem commented

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

Author

Owner

@J3n50m4t commented on GitHub (Feb 18, 2017):

As I wrote it now works I can't help to reproduce, sorry.
I deleted all logs but still here.

ts3server@server:~$ find ./* -name 'ts3server*_0.log'
./serverfiles/logs/ts3server_2017-02-18__15_10_51.508109_0.log

@J3n50m4t commented on GitHub (Feb 18, 2017): As I wrote it now works I can't help to reproduce, sorry. I deleted all logs but still here. ``` ts3server@server:~$ find ./* -name 'ts3server*_0.log' ./serverfiles/logs/ts3server_2017-02-18__15_10_51.508109_0.log ```

kerem commented

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

Author

Owner

@lock[bot] commented on GitHub (Jul 18, 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 18, 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.