MySQL Router increment error
Posted by: Kai Koppelmann
Date: August 11, 2023 03:09AM
Date: August 11, 2023 03:09AM
Hello,
I have a problem using MySQL Router on Windows Server systems (Linux works well). Version is 8.0.32 (tested with 8.0.34 as well).
Server plattforms are Server 2012 & 2019 (problem on both versions).
I bootstrapped a Router Instance on a single VM.
Bootstrapping worked like a charm:
mysqlrouter --bootstrap="<URI>" --conf-base-port=7446 --directory="C:\OracleMySQL\MySQLRouter80\Cluster-Production" --name="Cluster-Production" --account=mysqlrouter --account-create=always
The server itself starts correctly:
2023-08-11 10:52:53 io INFO [264c] starting 4 io-threads, using backend 'poll'
2023-08-11 10:52:53 http_server INFO [264c] listening on 0.0.0.0:8443
2023-08-11 10:52:53 metadata_cache_plugin INFO [2614] Starting Metadata Cache
2023-08-11 10:52:53 routing INFO [357c] [routing:bootstrap_ro] started: routing strategy = round-robin-with-fallback
2023-08-11 10:52:53 metadata_cache INFO [2614] Connections using ssl_mode 'PREFERRED'
2023-08-11 10:52:53 metadata_cache INFO [2ef4] Starting metadata cache refresh thread
2023-08-11 10:52:53 routing INFO [2be4] [routing:bootstrap_x_ro] started: routing strategy = round-robin-with-fallback
2023-08-11 10:52:53 routing INFO [2be4] Start accepting connections for routing routing:bootstrap_x_ro listening on 7449
2023-08-11 10:52:53 routing INFO [35d8] [routing:bootstrap_x_rw] started: routing strategy = first-available
2023-08-11 10:52:53 routing INFO [35d8] Start accepting connections for routing routing:bootstrap_x_rw listening on 7448
2023-08-11 10:52:53 routing INFO [1f14] [routing:bootstrap_rw] started: routing strategy = first-available
2023-08-11 10:52:53 routing INFO [1f14] Start accepting connections for routing routing:bootstrap_rw listening on 7446
2023-08-11 10:52:53 routing INFO [357c] Start accepting connections for routing routing:bootstrap_ro listening on 7447
2023-08-11 10:52:53 metadata_cache INFO [2ef4] Connected with metadata server running on VOMQMGTP0001.t1r.afomcs.com:3306
2023-08-11 10:52:53 metadata_cache INFO [2ef4] Potential changes detected in cluster after metadata refresh (view_id=0)
2023-08-11 10:52:53 metadata_cache INFO [2ef4] Metadata for cluster 'A41_DBS_Cluster_Icinga_Production_Site_A' has 1 member(s), single-primary:
2023-08-11 10:52:53 metadata_cache INFO [2ef4] <Server>:3306 / 33060 - mode=RW
Only one active member is intended at this point of the project.
Then I get error messages every 2-3 minutes logged in the MySQL Router log:
2023-08-11 10:57:16 routing INFO [34d4] [routing:bootstrap_rw] 127.0.0.1:51378 closed connection before finishing handshake
2023-08-11 10:57:16 routing INFO [34d4] [routing:bootstrap_rw] incrementing error counter for host of 127.0.0.1:51378 (now 1)
2023-08-11 10:57:43 routing INFO [3374] [routing:bootstrap_rw] 127.0.0.1:51450 closed connection before finishing handshake
2023-08-11 10:57:43 routing INFO [3374] [routing:bootstrap_rw] incrementing error counter for host of 127.0.0.1:51450 (now 2)
2023-08-11 10:58:27 routing INFO [326c] [routing:bootstrap_rw] 127.0.0.1:51558 closed connection before finishing handshake
2023-08-11 10:58:27 routing INFO [326c] [routing:bootstrap_rw] incrementing error counter for host of 127.0.0.1:51558 (now 3)
2023-08-11 10:58:53 routing INFO [204c] [routing:bootstrap_rw] 127.0.0.1:51630 closed connection before finishing handshake
2023-08-11 10:58:53 routing INFO [204c] [routing:bootstrap_rw] incrementing error counter for host of 127.0.0.1:51630 (now 4)
2023-08-11 11:00:04 routing INFO [34d4] [routing:bootstrap_rw] 127.0.0.1:51799 closed connection before finishing handshake
2023-08-11 11:00:04 routing INFO [34d4] [routing:bootstrap_rw] incrementing error counter for host of 127.0.0.1:51799 (now 5)
What I did so far:
- I started the Router using Verbose mode, no further information is logged.
- I changed the plugin for the created user "mysqlrouter" from mysql_native_password (seems to be the default in my case" to caching_sha2_password
- I bootstrapped into another directory on another drive
- I checked I bootstrapped using a cmd prompt ran as Administrator
- I checked the Connection Control Plugin - It tracks these entries:
''@'<IP>'
The user part is empty - is that normal?
- I updated version 8.0.32 to 8.0.34
I am glad for every single idea or hint how to solve this issue.
Many regards
Kai
I have a problem using MySQL Router on Windows Server systems (Linux works well). Version is 8.0.32 (tested with 8.0.34 as well).
Server plattforms are Server 2012 & 2019 (problem on both versions).
I bootstrapped a Router Instance on a single VM.
Bootstrapping worked like a charm:
mysqlrouter --bootstrap="<URI>" --conf-base-port=7446 --directory="C:\OracleMySQL\MySQLRouter80\Cluster-Production" --name="Cluster-Production" --account=mysqlrouter --account-create=always
The server itself starts correctly:
2023-08-11 10:52:53 io INFO [264c] starting 4 io-threads, using backend 'poll'
2023-08-11 10:52:53 http_server INFO [264c] listening on 0.0.0.0:8443
2023-08-11 10:52:53 metadata_cache_plugin INFO [2614] Starting Metadata Cache
2023-08-11 10:52:53 routing INFO [357c] [routing:bootstrap_ro] started: routing strategy = round-robin-with-fallback
2023-08-11 10:52:53 metadata_cache INFO [2614] Connections using ssl_mode 'PREFERRED'
2023-08-11 10:52:53 metadata_cache INFO [2ef4] Starting metadata cache refresh thread
2023-08-11 10:52:53 routing INFO [2be4] [routing:bootstrap_x_ro] started: routing strategy = round-robin-with-fallback
2023-08-11 10:52:53 routing INFO [2be4] Start accepting connections for routing routing:bootstrap_x_ro listening on 7449
2023-08-11 10:52:53 routing INFO [35d8] [routing:bootstrap_x_rw] started: routing strategy = first-available
2023-08-11 10:52:53 routing INFO [35d8] Start accepting connections for routing routing:bootstrap_x_rw listening on 7448
2023-08-11 10:52:53 routing INFO [1f14] [routing:bootstrap_rw] started: routing strategy = first-available
2023-08-11 10:52:53 routing INFO [1f14] Start accepting connections for routing routing:bootstrap_rw listening on 7446
2023-08-11 10:52:53 routing INFO [357c] Start accepting connections for routing routing:bootstrap_ro listening on 7447
2023-08-11 10:52:53 metadata_cache INFO [2ef4] Connected with metadata server running on VOMQMGTP0001.t1r.afomcs.com:3306
2023-08-11 10:52:53 metadata_cache INFO [2ef4] Potential changes detected in cluster after metadata refresh (view_id=0)
2023-08-11 10:52:53 metadata_cache INFO [2ef4] Metadata for cluster 'A41_DBS_Cluster_Icinga_Production_Site_A' has 1 member(s), single-primary:
2023-08-11 10:52:53 metadata_cache INFO [2ef4] <Server>:3306 / 33060 - mode=RW
Only one active member is intended at this point of the project.
Then I get error messages every 2-3 minutes logged in the MySQL Router log:
2023-08-11 10:57:16 routing INFO [34d4] [routing:bootstrap_rw] 127.0.0.1:51378 closed connection before finishing handshake
2023-08-11 10:57:16 routing INFO [34d4] [routing:bootstrap_rw] incrementing error counter for host of 127.0.0.1:51378 (now 1)
2023-08-11 10:57:43 routing INFO [3374] [routing:bootstrap_rw] 127.0.0.1:51450 closed connection before finishing handshake
2023-08-11 10:57:43 routing INFO [3374] [routing:bootstrap_rw] incrementing error counter for host of 127.0.0.1:51450 (now 2)
2023-08-11 10:58:27 routing INFO [326c] [routing:bootstrap_rw] 127.0.0.1:51558 closed connection before finishing handshake
2023-08-11 10:58:27 routing INFO [326c] [routing:bootstrap_rw] incrementing error counter for host of 127.0.0.1:51558 (now 3)
2023-08-11 10:58:53 routing INFO [204c] [routing:bootstrap_rw] 127.0.0.1:51630 closed connection before finishing handshake
2023-08-11 10:58:53 routing INFO [204c] [routing:bootstrap_rw] incrementing error counter for host of 127.0.0.1:51630 (now 4)
2023-08-11 11:00:04 routing INFO [34d4] [routing:bootstrap_rw] 127.0.0.1:51799 closed connection before finishing handshake
2023-08-11 11:00:04 routing INFO [34d4] [routing:bootstrap_rw] incrementing error counter for host of 127.0.0.1:51799 (now 5)
What I did so far:
- I started the Router using Verbose mode, no further information is logged.
- I changed the plugin for the created user "mysqlrouter" from mysql_native_password (seems to be the default in my case" to caching_sha2_password
- I bootstrapped into another directory on another drive
- I checked I bootstrapped using a cmd prompt ran as Administrator
- I checked the Connection Control Plugin - It tracks these entries:
''@'<IP>'
The user part is empty - is that normal?
- I updated version 8.0.32 to 8.0.34
I am glad for every single idea or hint how to solve this issue.
Many regards
Kai
Subject
Views
Written By
Posted
Sorry, you can't reply to this topic. It has been closed.
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.