Ariador

After upgrading my Ubuntu to 19.10 Eoan I've found realmd service is failing to start, with the status message as follows: [email protected]:~# systemctl status realmd ● realmd.service - Realmd service Loaded: loaded (/etc/systemd/system/realmd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2019-10-29 18:36:40 EET; 19s ago Process: 9271 ExecStart=/mangos/two/bin/realmd -c /mangos/two/etc/realmd.conf (code=exited, status=127) Main PID: 9271 (code=exited, status=127) Oct 29 18:36:40 ASUS1 systemd[1]: Started Realmd service. Oct 29 18:36:40 ASUS1 realmd[9271]: /mangos/two/bin/realmd: error while loading shared libraries: libmysqlclient.so.20: cannot open shared object file: No such file or directory Oct 29 18:36:40 ASUS1 systemd[1]: realmd.service: Main process exited, code=exited, status=127/n/a Oct 29 18:36:40 ASUS1 systemd[1]: realmd.service: Failed with result 'exit-code'. Actually, my installation of MySQL 8.0 has no such lib libmysqlclient.so.20 at all, at it seems to me a bit odd to look for and put some foreign libmysqlclient.so.20 to my /usr/lib just to have realmd to find something with a correct name. Could anyone recommend a normal fix for this problem?

Thanks Mr. MadMax, thanks Mr. Antz! I'll definitely send further bug reports (if any:) to /bug-tracker!

This is not a question, I simply could not find bug reporting thread, so writing it here. I've compiled most recent MaNGOS Two 0.21 at Ubuntu 19.04 with MySQL, everything passed just fine. Got complete client 3.3.5a (12340) from some site, checked it for completeness - works good, Vanilla, BK, WoTL all available at that site. Extracted dbc, maps, vmaps, mmaps with no errors at all, set realmd and mangosd to start as daemons (as recommended by Talendrys - my personal thanks for perfect installation guide). Just had to correct priorities in mangosd.conf - LogLevel from 3 to 0 and LogFilelevel from 0 to 1 to avoid endless events loop in mangosd console when starting it manually. Well, mangosd shows lots of database mistakes when starting - incorrect spell targets, incorrect paths for monsters - but all these are non-ctitilal, it starts well. Then, when checking playability. I've found that predefined characters aren't able to go to BK and WoTLK areas, run within the Classic content only. Client says something kinda 'You must have BK/WoTLK expansion to be installed to go here or there'. Config.wtf says - SET accounttype "CL". Changing to "BK" or "LK" doesn't work indeed, it respawns at every client start. Checked mangosd.conf variable Expansion - it is set to 2 by default, it's okay. It took me a while to find that default accounts at MaNGOS Two 0.21 are set to use no expansion: column 'expansion' at table realm.account shows all zeroes. Why don't to correct this small omittance? Also it would be good to put LogLevel=0 and LogFileLevel=1 values into mangosd.conf (if it also fits for other systems than Linux).

For ServerTwo there is currently a problem with creating databases (step 22). The dbTwo\Tools directory appeared to contain outdated mysql.exe and mysqldump.exe. To proceed I had to replace these with actual files from my \MySQL\MySQL Server 8.0\bin

I can participate with Translation English2Russian. Contact me at [email protected]