Bug #98914 MySQL Router no longer listens on configured ports
Submitted: 11 Mar 2020 18:28 Modified: 20 Mar 2020 20:30
Reporter: LE LAURENT Email Updates:
Status: Closed Impact on me:
Category:MySQL Router Severity:S3 (Non-critical)
Version:8.0.17 8.0.19 OS:Debian
Assigned to: Andrzej Religa CPU Architecture:Any
Tags: MySQL routeur reboot

[11 Mar 2020 18:28] LE LAURENT
after a server reboot (Debian 9 and 10), the mysql-router service is started but no longer listens on ports defined in the configuration file.

response to a boostrap attempt:

# Reconfiguring system MySQL Router instance...

- Fetching password for current account (mysql_router1_3v9uwd3gvic9) from keyring
Error: Failed retrieving password for user 'mysql_router1_xxxxxxxxxxxx' from keyring: Failed to open keyring file: /run/mysqlrouter/keyring: No such file or directory

installation method used:
dpkg -i mysql-router-commercial_8.0.XX+commercial-1debian9_amd64.deb
dpkg -i mysql-router_8.0.XX+commercial-1debian9_amd64.deb


dpkg -i mysql-apt-config_0.8.13-1_all.deb
apt-get update
apt-get install mysql-router

How to repeat:
restart server

Suggested fix:
- remove configuration files
   - /etc/mysqlrouter/mysqlrouter.conf
   - /etc/mysqlrouter/mysqlrouter.key 
- execute bootstrap command:
- reload the service
[20 Mar 2020 20:30] Philip Olson
Posted by developer:
Fixed as of the upcoming MySQL Router 8.0.20 release, and here's the proposed changelog entry from the documentation team:

Router's default data directory on Debian (/var/run/mysqlrouter) was not
preserved between system resets. Both the keyring and state.json files
were stored here, so Router could not function after a system reset. Now
/var/lib/mysqlrouter is used instead. In addition, the installation
process now detects and moves an existing configuration file to the new

Thank you for the bug report.