charmed-mysql.mysqlrouter-service daemon must be restarted if MySQL operator is restarted
#105
Comments
@NucciTheBoss |
carlcsaposs-canonical
closed this as not planned
|
Able to reproduce with above steps to reproduce, replacing |
|
Able to reproduce with |
|
The issue is with I typed up the steps to reproduce from memory. We have the issue with the Data Platform channel; it's the one that we use in our integration tests. Sorry about that. |
|
Unable to reproduce when connecting to mysql-router over TCP; issue appears to be socket related |
|
Appears to be a MySQL Router bug resolved in 8.0.35
https://dev.mysql.com/doc/relnotes/mysql-router/8.0/en/news-8-0-35.html |
|
Should be fixed by #103 |
|
Fix released as rev 135/136. Note that MySQL Router is now 8.0.35 instead of 8.0.34 |
|
Great! Thank you for your work Carl. I appreciate it 🚀
…On Wed, Feb 7, 2024, 4:18 AM Carl Csaposs ***@***.***> wrote:
Fix released as rev 135/136. Note that MySQL Router is now 8.0.35 instead
of 8.0.34
—
Reply to this email directly, view it on GitHub
<#105 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJTZFOQVIX6OLIYASOP6JTDYSNBFRAVCNFSM6AAAAABCU6AMA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZRGYYDOMJSGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Steps to reproduce
juju deploy slurmctld --channel edgejuju deploy slurmd --channel edgejuju deploy slurmdbd --channel edgejuju deploy slurmrestd --channel edgejuju deploy mysql --channel 8.0/edgejuju deploy mysql-router slurmdbd-mysql-router --channel 8.0/edgejuju integrate slurmctld:slurmd slurmd:slurmdjuju integrate slurmctld:slurmdbd slurmdbd:slurmdbdjuju integrate slurmctld:slurmrestd slurmrestd:slurmrestdjuju integrate slurmdbd:database slurmdbd-mysql-router:databasejuju integrate slurmdbd-mysql-router:backend-database mysql:databasejuju ssh mysql/leadersudo systemctl rebootjuju ssh slurmdbd/leadercat /var/log/slurm/slurmdbd.logsnap restart charmed-mysql.mysqlrouter-servicecat /var/log/slurm/slurmdbd.logExpected behavior
The behavior that we expect to see is that the slurmdbd daemon is able to successfully contact the MySQL database through the MySQL router Unix socket after the MySQL operator has been rebooted by a human operator.
Actual behavior
Even though the MySQL operator successfully reaches active status after we restart the machine MySQL is deployed to (used to not be the case), we still need to ssh into the slurmdbd operator and manually restart the mysql router service. Slurmdbd's log file indicates that it is not able to contact the MySQL database until we restart the MySQL router service
Versions
Operating system: Ubuntu 22.04 LTS on amd64
Juju CLI: 3.1.7-genericlinux-amd64
Juju agent: 3.1.6
mysql charm revision: 207
mysql-router charm revision: 127
LXD: 5.20
Log output
/var/log/slurm/slurmdbd.log just contains messages about being unable to establish a successful connection with the MySQL database. The desired message you want to see (means that slurmdbd is fully operational) in the log file is the following:
slurmdbd version 23.02.7 startedAdditional context
We must restart our machines because we need to load kernel modules to enable specific high-performance networking features on our machines. We originally had a similar reboot issue with mysql-operator, but this was fixed by canonical/mysql-operator#380
The text was updated successfully, but these errors were encountered: