I wanted to upgrade my server to 3.13.0 this morning. Unfortunately, I also got the error message that the update failed because the database could not be updated.
2020-11-11 06:01:59.385849|ERROR |SQL | |database update to revision: 34 failed!
My server doesn’t use a MySQL database, only the MySQL Lite version. (Please forgive me for not being able to post the exact error message because I wanted to get the whole thing done before work) The file update_34.sql not existed?!
Is that also so that I have to copy the mysqllib2.so file into the root directory?
What I don’t understand: I don’t use an external database, but use the SQL-Lite database. Then why does this error occur? I would only be interested for the sake of interest
Oh … almost forgotten:
is it actually enough if I simply rename the whitelist and blacklist?
Oh thanks don’t worry I do have a full backup of everything when I update so I restore everything to the way it was when things aren’t working I learned this the hard way XD to keep backup all the time
I wanted to give feedback: I installed server version 3.13.1 on my server this morning. It’s been running without any problems so far. I thought I can post the error message to you.
Now it’s going perfectly. I really didn’t understand why there were problems - despite that I use the SQLLite database - who knows.
The title says ‘TeamSepak’. Anyway, any news on the docker image besides ‘soon’? Why don’t you guys prepare this first and release on all platforms at the same time? Asking for a friend!
Hi there. The “location” parameter is not documented in the latest serverquery documentation. Do I need this parameter to access the location when an alternate GeoIP database is being used?
Am I correct when I estimate that there are hidden costs adopting ip2location geolocation pg services? For pg that is…
Following up, and evaluating the distance between an installed pg and ready for ts3 support… Problem is, the requirement of ip4r may be a non starter, or at least not without a ready-to-install pg extension.
The difficulty is, ip4r is not a baked-in supported extension. And building it, at least in a W10 environment, is challenging.
So… if pg is a non-starter, what is a ready alternative.