Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Thulium last won the day on January 25 2019

Thulium had the most liked content!

Community Reputation

14 Good

About Thulium

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hey, Did you install the trinitycore-database3.3.5 package as well? It's supposed to be in /opt/trinitycore/bin and that is added to your PATH variable (hence why you don't need to type in the whole path). The database package is not installed automatically, in case you want to run it on a different server.
  2. Hi all, It took me a whole lot some time to prepare my Debian 10 buildserver, but I finally got around to do so. Please find new packages up in the repo! I have updated the TS with the new paths. Please note that builds for Trinitycore on Debian 9 have been broken for a month or 2 because some of the build dependencies changed to versions that are not available in Debian 9 (for example SSL). Also, I'm winding down on my own server as I don't play WoW any more. I will keep compiling the packages for the forseeable future, but I will not port them to Debian 11 (slated for ~Q2 2021). Please find all the scripts and recipes in the TS to roll your own :-)
  3. The password it asks is the one for the database server root, the generated password is for the TC databases, so you probably installed a DB server and secured that beforehand. Most default installations of MariaDB on Debian don't request a password if you are logged in as root on the system and run mysql commands. Buster packages are coming up soon, just a few more days until it's (long awaited) release...... :-)
  4. It took me some time to set this up properly ;-) I'm glad it works well :-) About the missing config keys, that's correct, the config files are still the same (from the ones I created back then) and are not updated (as it requires me to reconfigure them each time a new key is added). Good thing for us is that the software doesn't care about missing keys and will assume a sane default value. The best/easiest solution would be to 'port' the configuration included in the packages to a fresh config file. Same goes for the warnings, the server will run just fine, but this is only because the DB is newer then the code, the other way around could be problematic, as you'd be referring to DB objects that don't exist for scripts that need 'm.
  5. Hey, I (very) recently updated the repo to use https, if you have issues downloading the packages, make sure you have apt-transport-https installed. When installing the server it does not automatically install the database packge, this allows you to use a different machine for the DB :-) (e.g. you already have a tuned DB server running). You can always install the DB package on the same host as the server package. It will pull in a mariadb-server as well. Not sure about the DB errors... The only check you can do is see if all trinitycore-*3.3.5 packages are of the same day, I just did and it seems the DB package is about 12 days newer. I'll need to check my buildserver why it isn't building the others. EDIT: found the issue, build was stuck on installing a dependency :-) just started it up again, expect new arrivals in ~2 hrs
  6. Well, in that case, roll your own ;-) https://github.com/Thulium-Drake/trinitycore-recipes
  7. psst, if you manage to get it working, don't forget to make a post on how you did it :-) help someone else help themselves too ;-)
  8. The documentation has everything you need: https://trinitycore.atlassian.net/wiki/spaces/tc/pages/2130077/Installation+Guide
  9. If you downloaded the Windows archive, you're going to have a hard time running the software.. Can you run 'file worldserver.exe', it should say something like: worldserver: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=9c04eb9ccf1cf2a97498f2b8aa4254aba44600ff, not stripped If you're running into issues with compiling and installing the software, have a look over here:
  10. Shameless plug: All the work you mention has already been done there ;-)
  11. Hi all, For those that are still using my packages, please note that the package name has changed! It's now suffixed with '-en', and I have put in place some scripting that will clean up old builds (as it was frequently clogging up my repo server). The name has changed due to me using the build script for other stuff as well and I want to avoid naming collisions with other software that resides in the repo. I have updated the TS :-) TL;DR: use trinitycore-server3.3.5-en, trinitycore-database3.3.5-en and trinitycore-tools3.3.5-en now.
  12. The other problem I see in the screenshot is that you are running Trinitycore as root... Please don't! It's very bad security practice. You'll want to create a new useraccount, and change permissions and test if everything still works. Shameless plug: the alternative -> Also features automatic updates.
  13. Hi @Wronglebowski, Yes, it was. For some reason my build script didn't include it any longer. I have updated it to include it again. I'm currently running a build and will upload new packages when that's done. Try to update your server in a few hours, as a new update is available and a full build takes about 2hrs. Cheers!
  14. Hi Folks, If anyone else comes across this topic in search of the missing script. Good news, it has been fixed in the latest version of the packages! For anyone wondering what this is all about? Check my topic mentioned in the post above mine. setup_database.sh is a script I wrote to setup a fresh set databases when you are using the packages I make. Cheers, Thulium
  15. Sorry for the late reaction, I've updated the database package to include the new TDB version. The name and the structure of the TDB archive on the Github page changed, so my script got confused, but I didn't use/check my server lately :-) Cheers!
  • Create New...