Meltie

@Перминов Алексей Doing the initial migration from one database to another can be a challenge for some not use to database structuring etc. I have done data migration from vMangos over to Mangos a few times a few months ago when playing with possible migration/transfer methods via SQL scripts.The best advise I can give you is to research the table structures within the character database itself, since account data is the most easiest to migrate. These will be the main tables to focus on below. Remember to study each table respectively per project. These tables below should remain the same across all projects with some naming differences. Achievements you wont have to worry about since original Classic (Vanilla) didn't have them yet. 1. Characters 2. Character Account Data 3. Character Achievements 4. Character Achievement Progression 5. Character Actions 6. Character Glyphs 7. Character Homebinds 8. Character Inventory: Includes item_instance table 9. Character Pets 10. Character Quest Status: Includes Daily, Weekly, Monthly, Rewarded and Seasonal 11. Character Reputation 12. Character Skills 13. Character Spells 14. Character Talent I may be able to help with the migration process as long as it's not related to public servers. I am planning to release these scripts publicly per project once I have all the methods ironed out 100% without issues. Best of luck!

Hello @Magissia! Compatibility of using different databases are very low as each project has their own structure builds for the databases. Migration from one project to another is possible but with a list of caveats. As for migrating account data, those structures haven't changed much since Mangos prime days. But here are a list of caveats you need to be aware of below. - Migrating character data with no data loss is vary slim and will require resetting most progression such as Skills, Skill Bars etc. - Character mail, auctions and some achievements as they are realm specific - such as Realm First Achievements. This does include some gifts as well. - Inventories of players can be the most pain in the butt when it comes to migration into existing database of players. New entries will need to be generated to fit the data without overwriting existing character data. If the destination database is empty, it's straight forward then. I've done a few migrations for some people that have requested it, but only have had 89% success rate with Mangos related projects. E.g. Mangos -> Trinity for example. When migrations are within the same project like Mangos Zero -> Mangos One, the success rate is much higher. If you want to chat about this on a deeper level, message me here or find me on Mangos Public Discord.

@Yogsoggoth You'll need to install OpenSSL 1.1.x, not OpenSSL 3.x. Ubuntu 22.04 ships with OpenSSL 3.x by default. Follow this below and you'll be up and running in no time. To remove OpenSSL 3.x sudo apt remove openssl libssl-dev Install OpenSSL 1.1.x # download binary openssl packages from Impish builds wget http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/openssl_1.1.1f-1ubuntu2.19_amd64.deb wget http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/libssl-dev_1.1.1f-1ubuntu2.19_amd64.deb wget http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1f-1ubuntu2.19_amd64.deb # install downloaded binary packages sudo dpkg -i libssl1.1_1.1.1f-1ubuntu2.19_amd64.deb sudo dpkg -i openssl_1.1.1f-1ubuntu2.19_amd64.deb sudo dpkg -i libssl-dev_1.1.1f-1ubuntu2.19_amd64.deb

Glad it's now working for you.

Those packages should be alright to remove, the system itself won't uninstall anything that it needs. If you are unsure, I would backup and/or snapshot the virtual machine before continuing. I've had that list pop up when I did the downgrade on OpenSSL and the system is working just fine. From my Ubuntu 22.04 machine. So I believe you'll be fine. If you need anymore help, feel free to message me.

First off you are only removing the libssl-dev and not openssl together. Remove related OpenSSL packages. sudo apt remove openssl libssl-dev Install OpenSSL 1.1.x # download binary openssl packages from Impish builds wget http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/openssl_1.1.1f-1ubuntu2.19_amd64.deb wget http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/libssl-dev_1.1.1f-1ubuntu2.19_amd64.deb wget http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1f-1ubuntu2.19_amd64.deb # install downloaded binary packages sudo dpkg -i libssl1.1_1.1.1f-1ubuntu2.19_amd64.deb sudo dpkg -i libssl-dev_1.1.1f-1ubuntu2.19_amd64.deb sudo dpkg -i openssl_1.1.1f-1ubuntu2.19_amd64.deb This is how I got around it on Ubuntu 22.04 for the time being.

You need to uninstall OpenSSL 3.x before attempting to use OpenSSL 1.1.x. Once OpenSSL 3.x is uninstalled, you'll have to install OpenSSL 1.1.x manually on the command line. I was doing some testing the past few days and how I got it to use the correct version. Note: OpenSSL 3.x support is on the way, but will take some time to make sure everything is working right.

Welcome to the community!

This bug does not exist in M3 (Cataclysm). Appears to exist only in M0 (Vanilla).

Segmentation fault is more then likely coming from the OpenSSL library, cause I've seen this happen on my local machines with version 3.x. Ubuntu 22.04 ships with OpenSSL 3.x by default. More then likely have to reinstall OpenSSL library with version 1.1.x instead of 3.x. Still need to implement proper messages within CMake itself to warn users using OpenSSL 3.x. I would try Ubuntu 21.10 or 20.04 and see if this happens again.

Changed Status to Confirmed Changed Implemented Version to Unset Changed Milestone to Unset Changed Priority to Normal Changed Sub-Category to Minor

I don't think the owner has had much time to work on this project lately. Might have to wait and see when they have the time to make some more progress on it. The user has been active recently. Just have to see what happens.

Changed Status to Completed Changed Implemented Version to 22.xx (Current Master Branch) Changed Milestone to Unset Changed Priority to New

Changed Status to Confirmed Changed Implemented Version to Unset Changed Milestone to Unset Changed Priority to Urgent

Changed Status to Confirmed Changed Implemented Version to 22.xx (Current Master Branch) Changed Milestone to Unset Changed Priority to High

Changed Status to Completed Changed Implemented Version to Unset

Changed Status to Completed

Changed Status to Completed Changed Implemented Version to Unset Changed Milestone to Unset Changed Priority to New Changed Sub-Category to Show Stopper

Changed Status to Completed

Awesome work! Did some research on the tracker and found similar issues with this. Hopefully this gets merged soon.

Changed Status to Duplicate

Welcome to the community Juggernaut! Contribution big or small is always welcomed. Hope to see some of your commits in the near futures.

Changed Status to Confirmed Changed Implemented Version to Unset Changed Milestone to Unset Changed Priority to Normal Changed Main Category to Realm Daemon

How to reproduce this issue as shown above on any client locale. Not restricted to French Locale. Set your RealmZone other then 0. Start your Realm Daemon. Login to any account and view the RealmList window. (If you only have one realm, nothing will appear)

@DaveJ61 A number of reason can cause this problem on Linux Systems. Here's a list that could be the cause but not limited too: Application doesn't have permission to run Application can't run properly do to missing libraries Mismatch between 32-bit and 64-bit libraries (should run, but could cause problems) Missing libraries after upgrading system image Can you look at your journal when trying to run the extractor tools and see what error are being throwing with better details on what is going on. Command to do that is journalctl -x. Linux dumps good logs if you know where to look. I hope this might help.