RE: DB Communication Link Failure

Hello Dag, Im not trying to do a multi-master setup, just recover my DB :/ I have installed a second node and connect it to the DB and it's not possible to connect to the database server automatically (but manually yes..) On the first node at each sql query sent, the service mysql restart on db

Re: DB Communication Link Failure

Your timeout configuration seems fine. There must be something wrong in your network. Or maybe in your MySQL service; as you said, it is restarting when you run commands against it. Therefore, it might be better to eliminate these issues first. On Mon, Jun 18, 2018 at 11:56 AM, Nicolas Bouige wro

Re: DB Communication Link Failure

Hi! This sound's like a corrupted database table. It's not that unusual mysqld are restarting after a query reqeuests values from a corrupted table space. That behaviour subsequently results in aborted connections. I'ld double check database consistency. The easist way to check against (at least

RE: DB Communication Link Failure

Hi Stephan, thanks for the command, i could spot which tables is corrupted : cloud.event Warning : InnoDB: Index 'i_event__created' contains 548 entries, should be 542. Warning : InnoDB: Index 'i_event__user_id' contains 547 entries, should be 542. Warning : InnoDB: Index 'i_event__account_i

Re: DB Communication Link Failure

Hi! there's also a --auto-repair switch that could be added to mysqlcheck --all-databases. But to be honest, you can't guarantee the content will match. So references to other tablefields might not match afterwards (well, i expect these references don't match right now either) As far as your r

RE: DB Communication Link Failure

Stephan, Thanks for your help, Unfortunately, the --auto-repair switch doesnt work as it's not support by the storage engine...and yes i dont have any backup without the corrupted tables. Nicolas Bouige DIMSI cloud.dimsi.fr 4, avenue Laurent Cely Tour d’Asnière – 92

Re: DB Communication Link Failure

Nicolas, I did not follow the thread properly, but as i saw this line about no backup and mysql corrupted files it got my attention. I had a similar problem once and i had used the Percona toolkit. It will not fix your DB but dump the data so you can reimport it Good luck. On Mon, Jun 18, 2018

RE: DB Communication Link Failure

Hi Leandro, i will take a look to this tool, thanks for the information ! Nicolas Bouige DIMSI cloud.dimsi.fr 4, avenue Laurent Cely Tour d’Asnière – 92600 Asnière sur Seine T/ +33 (0)6 28 98 53 40 De : Leandro Mendes Envoyé : lundi

RE: DB Communication Link Failure

Hello All, My DB is now up and running. i just executed the following commands : mysql > alter table cloud.event engine = innoDB mysql> check table cloud.event The check command give me an "OK", so i restarted the cloudstack-management. Now, all is good. Thanks you all for your help ! Ni