Comments on: Using dbdeployer to manage MySQL, Percona Server and MariaDB sandboxes https://www.percona.com/blog/using-dbdeployer-to-manage-mysql-percona-server-and-mariadb-sandboxes/ Tue, 06 Aug 2019 20:03:27 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: Agustín https://www.percona.com/blog/using-dbdeployer-to-manage-mysql-percona-server-and-mariadb-sandboxes/#comment-10970317 Mon, 18 Feb 2019 17:56:35 +0000 https://www.percona.com/blog/?p=50291#comment-10970317 Thanks for pointing this out, Giuseppe!

]]>
By: datacharmer https://www.percona.com/blog/using-dbdeployer-to-manage-mysql-percona-server-and-mariadb-sandboxes/#comment-10970272 Sun, 10 Feb 2019 19:15:50 +0000 https://www.percona.com/blog/?p=50291#comment-10970272 Sorry for seeing this article that late after publication.
Thanks for covering the tool.
Regarding your assertion “useful for setting up environments that are not already covered by the tool, like Galera clusters or semi-sync replication”, be aware that dbdeployer can run semi-synchronous replication out of the box

$ dbdeployer deploy replication 5.7 –semi-sync –concurrent
# 5.7 => 5.7.25
$HOME/sandboxes/rsandbox_5_7_25/initialize_slaves
initializing slave 1
initializing slave 2
Replication directory installed in $HOME/sandboxes/rsandbox_5_7_25
run ‘dbdeployer usage multiple’ for basic instructions’

$ ~/sandboxes/rsandbox_5_7_25/test_replication
# master log: mysql-bin.000001 – Position: 10577 – Rows: 20
# Testing slave #1
ok – slave #1 acknowledged reception of transactions from master
ok – slave #1 IO thread is running
ok – slave #1 SQL thread is running
ok – Table t1 found on slave #1
ok – Table t1 has 20 rows on #1
# Testing slave #2
ok – slave #2 acknowledged reception of transactions from master
ok – slave #2 IO thread is running
ok – slave #2 SQL thread is running
ok – Table t1 found on slave #2
ok – Table t1 has 20 rows on #2
# Tests : 10
# failed: 0 ( 0.0%)
# PASSED: 10 (100.0%)
# exit code: 0

$ ~/sandboxes/rsandbox_5_7_25/m -e ‘show status like “%yes%”‘
+—————————–+——-+
| Variable_name | Value |
+—————————–+——-+
| Rpl_semi_sync_master_yes_tx | 23 |
+—————————–+——-+

]]>
By: Agustín https://www.percona.com/blog/using-dbdeployer-to-manage-mysql-percona-server-and-mariadb-sandboxes/#comment-10970024 Mon, 03 Dec 2018 23:03:13 +0000 https://www.percona.com/blog/?p=50291#comment-10970024 Hi Bajrang!

Yes, you will need to have a binary tarball for the OS you are using. Unfortunately, we don’t ship MacOS images for Percona Server, so you will have to use the Linux ones. This will mean you will have to install a VM with Linux, and use dbdeployer inside it, if you want to try out Percona Server images. Another option here is for you to use Percona Server for Docker, which will work nicely in your MacOS, too: https://www.percona.com/doc/percona-server/5.7/installation/docker.html

Best,
Agustín.

]]>
By: Bajrang Panigrahi https://www.percona.com/blog/using-dbdeployer-to-manage-mysql-percona-server-and-mariadb-sandboxes/#comment-10969990 Sun, 25 Nov 2018 18:27:55 +0000 https://www.percona.com/blog/?p=50291#comment-10969990 Hi Agustin,

I had earlier tried using mysql sandbox for some replication topology testing,

Also tried out some time back, the DB deployer but never found a way to install in my local MAC machine as there is no binary available for Percona Server on Mac OS.

A *BINARY* TARBALL of Percona Server 5.7.22 for Mac OS, is required in order to test with DB deployer, on a MAC OS.

As DB Deployer does not quite work with the source tar-balls.,

Below is the ERROR when I run for the Percona server 5.7.22 source tarball :-

bpanigrahi$ dbdeployer deploy single ps5.7.22
——————————————————————————–
Looking for *darwin* binaries
——————————————————————————–
# Found the following:
/Users/bpanigrahi/opt/mysql/ps5.7.22/sql/table.h – tarball type: ‘source’ (flavor: any)
THIS IS A SOURCE TARBALL. YOU NEED TO USE A *BINARY* TARBALL
——————————————————————————–
Could not find any of the expected files for darwin server: [lib/libperconaserverclient.dylib lib/libmysqlclient.dylib]

MySQL 5.7, 8.0 provide the tar ball binary for Mac OS,
Is there a way where we can get the Percona Server tar ball binaries for Mac?

Last update on tarball binaries was seen for PS server 5.5 as posted by Vadim Tkachenko
https://www.percona.com/blog/2011/05/02/percona-server-and-xtrabackup-for-macos-experimental-binaries/

Thanks,
Bajrang

]]>
By: Agustin G https://www.percona.com/blog/using-dbdeployer-to-manage-mysql-percona-server-and-mariadb-sandboxes/#comment-10969259 Mon, 28 May 2018 03:38:30 +0000 https://www.percona.com/blog/?p=50291#comment-10969259 Hi Anil,

First, let me say that the correct place to send these kinds of questions is https://www.percona.com/forums/

Regarding the errors you are getting, you should check the mysql error log located in /home/mysql8/msb_8_0_11/data/msandbox.err

]]>
By: anil joshi https://www.percona.com/blog/using-dbdeployer-to-manage-mysql-percona-server-and-mariadb-sandboxes/#comment-10969248 Fri, 25 May 2018 12:24:24 +0000 https://www.percona.com/blog/?p=50291#comment-10969248 Thanks for sharing this.

I have used this and also got some error. If possible please have a look upon this

Using centos 6.8 on amazon azure.

[root@vm1 home]# dbdeployer –sandbox-binary=/opt/mysql/ –sandbox-home=/home/mysql8 deploy single 8.0.11

Database installed in /home/mysql8/msb_8_0_11
run ‘dbdeployer usage single’ for basic instructions’
err: exit status 1
cmd: &exec.Cmd{Path:”/home/mysql8/msb_8_0_11/start”, Args:[]string{“/home/mysql8/msb_8_0_11/start”, “”}, Env:[]string(nil), Dir:””, Stdin:io.Reader(nil), Stdout:(*bytes.Buffer)(0x1927bb00), Stderr:(*exec.prefixSuffixSaver)(0x1939aea0), ExtraFiles:[]*os.File(nil), SysProcAttr:(*syscall.SysProcAttr)(nil), Process:(*os.Process)(0x19118c90), ProcessState:(*os.ProcessState)(0x1910aba0), ctx:context.Context(nil), lookPathErr:error(nil), finished:true, childFiles:[]*os.File{(*os.File)(0x19378b98), (*os.File)(0x19378bb8), (*os.File)(0x19378bd8)}, closeAfterStart:[]io.Closer{(*os.File)(0x19378b98), (*os.File)(0x19378bb8), (*os.File)(0x19378bd8)}, closeAfterWait:[]io.Closer{(*os.File)(0x19378bb0), (*os.File)(0x19378bd0)}, goroutine:[]func() error{(func() error)(0x813d2b0), (func() error)(0x813d2b0)}, errch:(chan error)(0x1932f900), waitDone:(chan struct {})(nil)}
stdout: …………………………………………………………………………………………………………………………………………………………….. sandbox server not started yet

]]>