Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.0.0
-
None
-
Linux
Description
This is imported from bugzilla item: http://bugs.mariadb.com/show_bug.cgi?id=656
Description Vilho Raatikka 2014-12-18 15:16:42 UTC
How to reproduce:
1. start rwsplit with a master and optionally with slaves
2. prevent connections to master by executing
iptables -I INPUT -p tcp --dport 3000 -j REJECT --reject-with icmp-admin-prohibited
3. read the message log:
(..errors..)
2014-12-18 17:09:30 Server 127.0.0.1:3000 lost the master status.
2014-12-18 17:09:30 Info: A Master Server is now available: 127.0.0.1:3000
2014-12-18 17:10:35 Info: A Master Server is now available: 127.0.0.1:3000
This is comment history from bugzilla:
Comment 1 Mark Riddoch 2015-02-13 10:28:46 UTC
Add as test case and retest
Comment 2 Timofey Turenko 2015-03-02 10:42:34 UTC
Error log says:
2015-03-02 12:36:31 Error : Monitor was unable to connect to server 192.168.122.141:3306 : "Can't connect to MySQL server on '192.168.122.141'
(111)"
Message log says:
2015-03-02 12:36:31 Server 192.168.122.141:3306 lost the master status.
2015-03-02 12:36:31 Info : A Master Server is now available: 192.168.122.141:3306
MaxAdmin says:
Server 0x26e71c0 (server1)
Server: 192.168.122.141
Status: Master, Down
Protocol: MySQLBackend
Port: 3306
Server Version: 5.5.42-MariaDB-log
Node Id: 141
Master Id: -1
Slave Ids: 142, 143 , 144
Repl Depth: 0
Number of connections: 0
Current no. of conns: 0
Current no. of operations: 0
So, the problem is visible only in the messages log. Is it a real problem or just logging issue?