Switch to Mariadb

[Drow 3]

 

Hello guys,

 

I wanted to ask what is the procedure to switch from mysel5.5 to mariadb10.3 or 10.4 ?

 

1) On what tables do I need to change from MyISAM to InnoDB.

2) Do I need to add in src the libs or is ok to leave it as it is.

3) What is the procedure to move the existing table if there is one.

 

What I did untill now is this:

For 1*, I did this:

ALTER TABLE accoount.account ENGINE=InnoDB;
ALTER TABLE player.player ENGINE=InnoDB;
ALTER TABLE player.item ENGINE=InnoDB, ROW_FORMAT=DYNAMIC;
ALTER TABLE player.affect ENGINE=InnoDB, ROW_FORMAT=DYNAMIC;
ALTER TABLE player.quest ENGINE=InnoDB;
ALTER TABLE player.player_deleted ENGINE=InnoDB;
ALTER TABLE player.player_index ENGINE=InnoDB, ROW_FORMAT=DYNAMIC;
ALTER TABLE player.safebox ENGINE=InnoDB;
ALTER TABLE player.item_award ENGINE=InnoDB;

2* I left it as it is

3* 

 

mysqldump -u root-p --all-databases --skip-lock-tables > alldb.sql (export) my tables that were using mysql5.5

after installing mardiadb10.3

mysql -u root -p < alldb.sql

 

and now my problem is this:

2020-06-15 15:33:53 80 [Warning] Aborted connection 80 to db: 'common' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 126 [Warning] Aborted connection 126 to db: 'player' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 64 [Warning] Aborted connection 64 to db: 'common' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 124 [Warning] Aborted connection 124 to db: 'player' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 70 [Warning] Aborted connection 70 to db: 'common' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 83 [Warning] Aborted connection 83 to db: 'log' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 127 [Warning] Aborted connection 127 to db: 'log' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 66 [Warning] Aborted connection 66 to db: 'common' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 74 [Warning] Aborted connection 74 to db: 'player' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 122 [Warning] Aborted connection 122 to db: 'common' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 73 [Warning] Aborted connection 73 to db: 'log' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 68 [Warning] Aborted connection 68 to db: 'log' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 75 [Warning] Aborted connection 75 to db: 'common' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 76 [Warning] Aborted connection 76 to db: 'player' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 72 [Warning] Aborted connection 72 to db: 'common' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 63 [Warning] Aborted connection 63 to db: 'player' user: 'root' host: 'localhost' (Got an error reading communication packets)
2020-06-15 15:33:53 78 [Warning] Aborted connection 78 to db: 'log' user: 'root' host: 'localhost' (Got an error reading communication packets)

 

and after a few second my cores are closing without any syserr.

 

Thanks, and I think that it will help some people in the future.

 

 

[IceShiva 150]

You need also to replace maria/mysql connector lib. Additionally you cant use InnoDB storage engine on metin2 server due to InnoDB is transaction level database and you have to manage behaviour like which data should be readed at this moment when specific row is now locked (read commited/read uncommited). So you also need to implement sql connector which support transactions.

Of course if you want still use InnoDB on metin2 server you should just update you connector this will fix errors as described on up post. But unwanted behaviour is guaranted.