profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/tanji/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Guillaume Lefranc tanji Signal 18 France https://signal18.io IT/OPS/DBA

signal18/replication-manager 489

Signal 18 repman - Replication Manager for MySQL / MariaDB / Percona Server

bstillman/bgbackup 57

A wrapper script for xtrabackup/innobackupex.

signal18/docs.signal18.io 0

Documentation repository for docs.signal18.io

tanji/admiral 0

Admiral is a lightweight Ansible inventory database management tool

tanji/ansible-elasticsearch 0

Ansible playbook for Elasticsearch

tanji/ansible-role-sensu-client 0

Sensu Client role for Ansible

tanji/ansible-role-sensu-server 0

Ansible role for Sensu server

tanji/ansible_lab 0

Playground for insible tests

tanji/awesome-mysql 0

A curated list of awesome MySQL software, libraries, tools and resources

issue commentsignal18/replication-manager

v2.0.2 http frequent js errors

Hi @lenovore we are not AngularJS experts, feel free to submit a PR to fix the issue. Also 2.0.x is EOL

lenovore

comment created time in 5 days

push eventsignal18/replication-manager

Guillaume Lefranc

commit sha 524f56a23830b191d0a6234d62f910449c7d2d4a

Update copyrights

view details

push time in 8 days

push eventsignal18/replication-manager

Guillaume Lefranc

commit sha ec39cdd9bc651d95dcf0bb69745e6c056c823e3d

Update copyrights

view details

Guillaume Lefranc

commit sha 90ba2b2eabcc34d1e68910bf5f884d542caedc10

Merge pull request #379 from signal18/copyright Update copyrights (2.1)

view details

push time in 8 days

PR opened signal18/replication-manager

Update copyrights (2.1)
+328 -158

0 comment

159 changed files

pr created time in 8 days

create barnchsignal18/replication-manager

branch : copyright

created branch time in 8 days

push eventsignal18/replication-manager

Guillaume Lefranc

commit sha d5b40f02c1a6078dadb6092460c20448dd81f3f6

Updates

view details

Guillaume Lefranc

commit sha 7081f449354daab07a48e941061e9a555ac3bbb8

Merge branch 'develop' of github.com:signal18/replication-manager into develop

view details

push time in a month

push eventsignal18/replication-manager

Guillaume Lefranc

commit sha 06ac9b2afaccb57d3aab4ddc099521b525c64095

More Dockerfile fixes

view details

push time in a month

push eventsignal18/replication-manager

Guillaume Lefranc

commit sha cc04da0040469b4484941204e46703e035837dd0

Dockerfile fixes

view details

push time in a month

push eventsignal18/replication-manager

Guillaume Lefranc

commit sha 736f1cae6b0d72a62c9ba5cb7cc787ac702ebb14

Deprecate alpine

view details

push time in a month

push eventsignal18/replication-manager

Guillaume Lefranc

commit sha e52a2748f888264aee9b99073dd915f98a68ae59

Fix branch name

view details

push time in a month

push eventsignal18/replication-manager

Guillaume Lefranc

commit sha 1418bd9571304d1a3b91e366571f116e9d2b91d0

New Dockerfile.pro based on debian slim

view details

Guillaume Lefranc

commit sha 89220a96f9acb22953f6930b1a1d77e40ce670e5

Bump up Go version

view details

Guillaume Lefranc

commit sha 59b77b6fd8035882bf419be9f260884fe9f80400

Commit Jenkinsfile

view details

push time in a month

push eventsignal18/replication-manager

Guillaume Lefranc

commit sha 9ac2086bfa284c6665ec19a05b803b867d4b1cf3

Commit Jenkinsfile

view details

push time in a month

push eventsignal18/replication-manager

Guillaume Lefranc

commit sha c3621d677cdc461c40e1ecbc26ca5d3c3f548dbf

New Dockerfile.pro based on debian slim

view details

push time in a month

issue closedsignal18/replication-manager

how install it on aarch

I want to use it on CentOS Linux release 7.9.2009 (AltArch),how can I install it?

closed time in 3 months

xiaomianlang

issue commentsignal18/replication-manager

how install it on aarch

Hi @xiaomianlang right now we don't provide an AltArch version I would recommend compiling from source, that is not too complex with the Makefile. We'll look at providing official ARM Versions. Let me know if you need help with the compile!

xiaomianlang

comment created time in 3 months

issue commentsignal18/replication-manager

[QA] MariaDB switchover failed: Prefered master: not found in database servers

You can find recommended settings for replication there: https://docs.signal18.io/howto/replication-best-practice

Maybe that should be clearer in our docs, I will make a note of improving installation notes.

leiless

comment created time in 3 months

issue closedsignal18/replication-manager

[QA] MariaDB switchover failed: Prefered master: not found in database servers

Hi, @svaroqui, @tanji, I'm a newbie to signal18/replication-manager, I believe I certainly misused/misconfiged replication-manager, I failed to perform replication switchover by replication-manager-cli console.

Yet after some search-out, I still have no idea how to solve it.

Env

  • Ubuntu 20.04 LTS kernel 5.8.0-55-generic x86_64
  • signal18/replication-manager v2.1.6
  • MariaDB 10.5.10-MariaDB-1:10.5.10+maria~focal-log with three servers(1 master, 2 replicas)

MariaDB master/replica config

I've deploy three MariaDB instances via Docker

$ docker network inspect semi-sync-net
        "Containers": {
            "0e0b9617b170dc46fed30606e685d944ace45dbd0157bede1e8a7a10753f5a5f": {
                "Name": "mariadb-13308",
                "IPv4Address": "172.31.254.3/24",
            },
            "b52106f2cf19dd512e134b3404a2da89ddb3091fab938a02a67c8f50215b78f8": {
                "Name": "mariadb-13307",
                "IPv4Address": "172.31.254.2/24",
            },
            "f78d4aa0a744b1d74668b2669ed31996964654becd59edea25f85b6d9918c1ae": {
                "Name": "mariadb-13306",
                "IPv4Address": "172.31.254.1/24",
            }
        }

$ docker container ls | grep mariadb
0e0b9617b170   mariadb:10.5-focal           "docker-entrypoint.s…"   4 hours ago   Up 4 hours   127.0.0.1:13308->3306/tcp 
  mariadb-13308
b52106f2cf19   mariadb:10.5-focal           "docker-entrypoint.s…"   4 hours ago   Up 4 hours   127.0.0.1:13307->3306/tcp 
  mariadb-13307
f78d4aa0a744   mariadb:10.5-focal           "docker-entrypoint.s…"   4 hours ago   Up 4 hours   127.0.0.1:13306->3306/tcp 
  mariadb-13306

By initial, 127.0.0.1:13306(172.31.254.1:3306 docker network) is the master node, the remaining two are replicas.

config.toml

[Default]
title = "MariaDBClusterTest"
db-servers-hosts = "127.0.0.1:13306,127.0.0.1:13307,127.0.0.1:13308"
db-servers-credential = "root:123456"
replication-credential = "repl:123456" # Q: is this config is ok? 'repl' user have only the REPLICATION SLAVE privilege.
failover-mode = "manual"
verbose=1

SHOW GRANTS

MariaDB [(none)]> SELECT user FROM mysql.user GROUP BY user \G
*************************** 1. row ***************************
User: mariadb.sys
*************************** 2. row ***************************
User: repl
*************************** 3. row ***************************
User: root
3 rows in set (0.002 sec)

MariaDB [(none)]> SHOW GRANTS FOR 'repl'@'172.31.254.%' \G
*************************** 1. row ***************************
Grants for repl@172.31.254.%: GRANT REPLICATION SLAVE ON *.* TO `repl`@`172.31.254.%` IDENTIFIED BY PASSWORD '*6BB4837EB74329105EE4568DDA7DC67ED2CA2AD9'
1 row in set (0.000 sec)

Logs

$ sudo ./replication-manager-osc --config config.toml monitor --http-server
WARN[2021-06-21T16:04:09+08:00] No include directory in default section      
WARN[2021-06-21T16:04:09+08:00] No monitoring-save-config variable in default section config change lost on restart 
INFO[2021-06-21T16:04:09+08:00] Replication-Manager started in daemon mode    version=v2.1.6
INFO[2021-06-21T16:04:09+08:00] No existing password encryption scheme        error="Key file does not exist"
INFO[2021-06-21T16:04:09+08:00] Failover in interactive mode                  cluster=Default
INFO[2021-06-21T16:04:09+08:00] No existing password encryption scheme in LoadAPIUsers  cluster=Default
INFO[2021-06-21T16:04:09+08:00] Starting HTTPS & JWT API on 0.0.0.0:10005    
INFO[2021-06-21T16:04:13+08:00] No file found: open /var/lib/replication-manager/Default/clusterstate.json: no such file or directory  cluster=Default
INFO[2021-06-21T16:04:13+08:00] No database TLS certificates                  cluster=Default
INFO[2021-06-21T16:04:13+08:00] No database previous TLS certificates         cluster=Default
INFO[2021-06-21T16:04:13+08:00] New database monitored: 127.0.0.1:13306       cluster=Default
INFO[2021-06-21T16:04:13+08:00] New database monitored: 127.0.0.1:13307       cluster=Default
INFO[2021-06-21T16:04:13+08:00] New database monitored: 127.0.0.1:13308       cluster=Default
INFO[2021-06-21T16:04:13+08:00] Loading 0 proxies                             cluster=Default
INFO[2021-06-21T16:04:13+08:00] Loading database configurator config /usr/share/replication-manager/opensvc/moduleset_mariadb.svc.mrm.db.json  cluster=Default
INFO[2021-06-21T16:04:13+08:00] Loading proxies configurator config /usr/share/replication-manager/opensvc/moduleset_mariadb.svc.mrm.proxy.json  cluster=Default
INFO[2021-06-21T16:04:13+08:00] Assigning a global connection on server 127.0.0.1:13307  cluster=Default
INFO[2021-06-21T16:04:13+08:00] Assigning a global connection on server 127.0.0.1:13308  cluster=Default
INFO[2021-06-21T16:04:13+08:00] Assigning a global connection on server 127.0.0.1:13306  cluster=Default
INFO[2021-06-21T16:04:13+08:00] Starting HTTP server on localhost:10001      
WARN[2021-06-21T16:04:15+08:00] Could not find a slave in topology            cluster=Default code=ERR00010 status=RESOLV type=state
WARN[2021-06-21T16:04:15+08:00] Could not find a master in topology           cluster=Default code=ERR00012 status=RESOLV type=state
WARN[2021-06-21T16:04:15+08:00] No GTID strict mode on slave 127.0.0.1:13307  cluster=Default code=WARN0058 status=OPENED type=state
WARN[2021-06-21T16:04:15+08:00] No compression of binlog on slave 127.0.0.1:13306  cluster=Default code=WARN0068 status=OPENED type=state
WARN[2021-06-21T16:04:15+08:00] No log-slave-updates on master 127.0.0.1:13306  cluster=Default code=WARN0069 status=OPENED type=state
WARN[2021-06-21T16:04:15+08:00] No candidates found in slaves list            cluster=Default code=ERR00032 status=OPENED type=state
WARN[2021-06-21T16:04:15+08:00] No GTID strict mode on master 127.0.0.1:13306  cluster=Default code=WARN0070 status=OPENED type=state
WARN[2021-06-21T16:04:15+08:00] Binary log disabled on slave: 127.0.0.1:13307  cluster=Default code=ERR00013 status=OPENED type=state
WARN[2021-06-21T16:04:15+08:00] No compression of binlog on slave 127.0.0.1:13307  cluster=Default code=WARN0056 status=OPENED type=state
WARN[2021-06-21T16:04:15+08:00] No log-slave-updates on slave 127.0.0.1:13307  cluster=Default code=WARN0057 status=OPENED type=state
WARN[2021-06-21T16:04:15+08:00] No Heartbeat <= 1s on master 127.0.0.1:13306  cluster=Default code=WARN0062 status=OPENED type=state
WARN[2021-06-21T16:04:15+08:00] No InnoDB durability on master 127.0.0.1:13306  cluster=Default code=WARN0064 status=OPENED type=state
WARN[2021-06-21T16:04:17+08:00] Cluster state down                            cluster=Default code=ERR00021 status=RESOLV type=state
WARN[2021-06-21T16:04:17+08:00] Master user 'repl'@'172.31.254.%!'(MISSING) is not defined on replication candidate 127.0.0.1:13307  cluster=Default code=ERR00056 status=OPENED type=state


INFO[2021-06-21T16:04:44+08:00] Rest API receive switchover request           cluster=Default
INFO[2021-06-21T16:04:44+08:00] API force for prefered master:                cluster=Default
INFO[2021-06-21T16:04:44+08:00] Prefered master: not found in database servers   cluster=Default
INFO[2021-06-21T16:04:44+08:00] --------------------------                    cluster=Default
INFO[2021-06-21T16:04:44+08:00] Starting master switchover                    cluster=Default
INFO[2021-06-21T16:04:44+08:00] --------------------------                    cluster=Default
INFO[2021-06-21T16:04:44+08:00] Checking long running updates on master 10    cluster=Default
INFO[2021-06-21T16:04:44+08:00] select SUM(ct) from ( select count(*) as ct from information_schema.processlist  where command = 'Query' and time >= ? and info not like 'select%!'(MISSING) union all select count(*) as ct  FROM  INFORMATION_SCHEMA.INNODB_TRX trx WHERE trx.trx_started < CURRENT_TIMESTAMP - INTERVAL ? SECOND) A(10)  cluster=Default module=MasterFailover server="127.0.0.1:13306"
INFO[2021-06-21T16:04:44+08:00] Flushing tables on master 127.0.0.1:13306     cluster=Default
INFO[2021-06-21T16:04:44+08:00] FLUSH NO_WRITE_TO_BINLOG TABLES               cluster=Default module=MasterFailover server="127.0.0.1:13306"
INFO[2021-06-21T16:04:44+08:00] Electing a new master                         cluster=Default
ERRO[2021-06-21T16:04:44+08:00] No candidates found                           cluster=Default


^CINFO[2021-06-21T16:04:51+08:00] RECEIVED SIGNAL: interrupt

closed time in 3 months

leiless

issue commentsignal18/replication-manager

[QA] MariaDB switchover failed: Prefered master: not found in database servers

@leiless it is not a bug, you need to configure your servers properly

bin_log enabled on all servers replication user with correct privilege

etc

leiless

comment created time in 3 months

issue commentsignal18/replication-manager

[QA] MariaDB switchover failed: Prefered master: not found in database servers

Hello, I can see a few errors that will cause you not to be able to make a failover:

the first is : ERR00013 Binary log disabled on slave. If your slaves don't have a binary log enabled they cannot be candidates. 2nd one: ERR00056 Replication user does not exist on current master, if your master is demoted to a slave it needs that user. Last one ERR00007 User must have REPLICATION SLAVE privilege.

Can you make sure all your databases have the required configuration?

leiless

comment created time in 3 months