MySQL Forums
Forum List  »  Router & Proxy

Re: MySQL Router - After client machine rebooting, Cannot connect to MySQL InnoDB Cluster
Posted by: 佳晃 富田
Date: November 28, 2019 11:41PM

After client machine rebooting, there are the following behavior.

1.
MySQL Router shows the following status.

# systemctl status mysqlrouter

● mysqlrouter.service - LSB: Start / Stop MySQL Router
Loaded: loaded (/etc/init.d/mysqlrouter; generated)
Active: active (exited) since Thu 2019-11-28 12:28:33 JST; 1 day 1h ago
Docs: man:systemd-sysv-generator(8)
Process: 162 ExecStart=/etc/init.d/mysqlrouter start (code=exited, status=0/SUCCESS)

11月 28 12:28:33 client systemd[1]: Starting LSB: Start / Stop MySQL Router...
11月 28 12:28:33 client mysqlrouter[162]: * Starting MySQL Router
11月 28 12:28:33 client mysqlrouter[162]: ...done.
11月 28 12:28:33 client systemd[1]: Started LSB: Start / Stop MySQL Router.


On the other hand,before rebooting, Active value is 'active(running)'.


2.
Configuration file(mysqlrouter.conf) shows keyring_path is '/run/mysqlrouter/keyring'.
But this keyring_path doesn't exist.


3.
Before rebooting, reading configuration process remains.

# ps aux|grep mysql
mysqlro+ 332 0.0 0.0 645184 11480 pts/0 Sl 13:29 0:14 mysqlrouter -c /etc/mysqlrouter/mysqlrouter.conf

But after rebooting, this process disappears.



Edited 1 time(s). Last edit at 11/28/2019 11:57PM by 佳晃 富田.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: MySQL Router - After client machine rebooting, Cannot connect to MySQL InnoDB Cluster
366
November 28, 2019 11:41PM


Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.