-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update doesnt work. #43
Comments
Thanks for reporting this problem. Please replace INSTANCE_PATH with the absolute path to your TS3 instance and LATEST_INSTANCE_LOG_FILE with the absolute path to your latest instance log file (_0.log) and execute these commands:
Have you installed expect and telnet? Which Operating System and version (eg. Debian 8.5) are you using? |
same problem TS3tools TS3UpdateScript Debug ReportDate and time of report: 20160826-1152 TS3UpdateScript outputPlease copy and paste the output of the shell below this line and/or attach a debug file of this script. Operating System DetailsLSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch Linux server.g3.lt 2.6.32-042stab116.2 #1 SMP Fri Jun 24 15:33:57 MSK 2016 x86_64 x86_64 x86_64 GNU/Linux root User localeLANG=C teamspeak User localeLANG=C TS3 Update DetailsUpdate path: 3.0.11.3 -> 3.0.13.3 INI Filests3server.inimachine_id= |
Perfect! First of all, you should get a warning message by your TeamSpeak 3 server due of the locale "C" (see issue #44). I recommend you, to fix that by setting it to UTF8. You should be able to change this by using the command
Anyway, I can just see this single problem:
Everything else looks fine. Please note, that the IP "0.0.0.0" in the ts3server.ini means, that your TS3 server instance is listening on all interfaces and IP addresses. If you want, that your server is only listening on a single IP, you have to set this IP there instead of "0.0.0.0".
Can you please show me your instance details from the output of the script? There should be written "0.0.0.0" as ServerQuery IP and not 127.0.0.1. Also, as I can see there, the script has detected amd64 and linux in your case. Is that wrong? What should be correct? |
this is VPS centos 6.8 :) TS3tools TS3UpdateScript Debug ReportDate and time of report: 20160826-1219 TS3UpdateScript outputPlease copy and paste the output of the shell below this line and/or attach a debug file of this script. Operating System DetailsLSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch Linux server.g3.lt 2.6.32-042stab116.2 #1 SMP Fri Jun 24 15:33:57 MSK 2016 x86_64 x86_64 x86_64 GNU/Linux root User localeLANG=C teamspeak User localeLANG=C TS3 Update DetailsUpdate path: 3.0.11.3 -> 3.0.13.3 INI Filests3server.inimachine_id= Database INI-file[config] Log filesInstance Log file2016-08-26 16:19:37.718914|INFO |ServerLibPriv | |TeamSpeak 3 Server 3.0.13.3 (2016-08-18 16:46:43) |
Starting to think about to update server manually :( |
I'm not very familiar with CentOS, but this article may help you, to change the locale: http://www.cyberciti.biz/faq/how-to-set-locales-i18n-on-a-linux-unix/ You may have already changed it, but need a further command or logout and in again to take effect. I believe, you missunderstand something. The
You can find this list here: http://teamspeak.com/downloads#server Due of that, there will never be written "CentOS", "Debian" or anything like that. That's not the TS3 Server Platform, but the operating system distribution. ;) Now, you've set What exactly do you interpret as issue? Just show me the output and let me know, what's wrong with that and I'll help you to fix or get that working. :) |
CENTOS is redhat linux :) root@server [/home/ts3]# ./TS3UpdateScript --inform-online-clients --check About: This is the most widely used and fastest shell script to update all your TeamSpeak 3 server instances. |_ / | / | | ___ ___ | |___ () __ / | ___ Script Version: 5.0.1 (2016-08-18) Donate and support this script: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=7ZRXLSC2UBVWE Please wait... Script is working... Performing self-tests as preventive measures against possible failures [ OK ] Collecting necessary information for further tasks [ OK ] All collected information were validated successfully as preventive measures against possible failures [ INFO ] 1 TeamSpeak 3 server instance found... Collecting as much as possible information for following TeamSpeak 3 server instance: /home/teamspeak
############################################################################ send: spawn id exp4 not open Trying to backup temporary server passwords. Please wait... |
Thanks for this output. Can you please send or link the debug file for your update process here? You need to use the parameter I believe, that you've the same issue like a few other customers. By starting the TS3 server instance it returns a "Segmentation fault" and due of that, the server crashes. I'm already working on a fix for that with TeamSpeak. |
P.S. i have change query ip to 0.0.0.0 cause monitor not working not time to search how to fix :) |
Yeah, no problem. The poking error should be fixed with the issue #45. Regarding the other issue, I'm currently talking to the TeamSpeak developers. But we think, that we've already found the reason for this cause. |
eta of fixing? :) APPROX. |
Hi, The update script detects my instance but cant connect to it, since it thinks the server query port is available on 127.0.0.1 - its not. I managed to modify the update script to use the correct IP > after that it doesnt know anything about amd64 / linux (which it should since it wanted me to install lsb_release ...) Anyways, I did update my teamspeak server, but doing so manually would've been faster probably :-D |
I will do same :) tomorrow if the will not push fixes :) |
@golimer With "Regarding the other issue" I mean fixing the real cause for the failed update. Should be fixed soon. :) @boindil So you've just updated the ServerQuery binding IP address within the database? I'm not sure, if that's a supported solution by TeamSpeak. :D I'll improve the script, to check the settings in the database too. What exactly did you change in the TS3UpdateScript? You may have just broken the script with your change. o.O |
@boindil Can you provide me some more information, please?
|
I've improved the ServerQuery IP detection and fixed the problem with the failed TS3 update process. |
If I'm correct thats the recommended solution .. I've never used a ts3server.ini file. Prior do changing the bindings I had a look at the teamspeak forums.
Yes, I'm pretty sure I did "break" the script. I replaced the important variables (IP, platform, architecture) with static strings. It did update correctly, but that was only a one time change to be able to update. I did revert the script after that. Still I am not sure, why the script did not detect the platform and architecture using lsb_release (which it asked me to install - error/warning during script update)
I did change all bindings |
@boindil Thanks for your feedback. Did you test the latest version of the TS3UpdateScript, if it's displaying the correct server details? |
Hi, |
Thanks for your feedback! |
Thank you for your hard work! |
Got to reopen this because I've updated my TS3 server today.
After waiting about 2 minutes, I pressed CTRL+C. The script proceeded after that. I guess it is related to this issue, but I'm not sure. |
I don't think, that it's related. Please create a new issue for that and attach, send or provide me a debug file. By the way: How many virtual servers are running on your instance? It's highly not recommend to use it as ATHP, because it's already taking a few minutes even when there are only 1 to 5 virtual servers. Here are already to much and old posts about something else. Thanks. |
On latest version (5.0.1) the instanceinfo is always wrong and thus the script cant download and update my instance.
It detects 127.0.0.1 as
SERVERQUERY_IP
, but I got two IPs and teamspeak is running on the secondary only. The script doesnt detect amd64 / linux as well.The text was updated successfully, but these errors were encountered: