Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.2.9
-
None
-
FreeBSD 11.1
Description
I am running galera multi-master. After upgrading one node from 10.2.7_1 to 10.2.9. I couldn't start it. When I run bash -x /usr/local/etc/rc.d/mysql-server start, I found that mysqld_safe is looking for "WSREP: Running position" in wsrep_recovery.XXXXXX. Not sure if this is related to MDEV-13950.
I compared mysqld_safe with another machine which is running 10.2.7_1.
--- /usr/local/bin/mysqld_safe 2017-09-12 23:14:57.000000000 +1000 |
+++ mysqld_safe.10.2.9 2017-10-13 15:17:02.066860000 +1100 |
@@ -245,7 +245,7 @@ |
local euid=$(id -u)
|
local ret=0 |
|
|
- local wr_logfile=$(mktemp $DATADIR/wsrep_recovery.XXXXXX)
|
+ local wr_logfile=$(mktemp wsrep_recovery.XXXXXX)
|
|
|
# safety checks
|
if [ -z $wr_logfile ]; then |
@@ -263,11 +263,11 @@ |
|
|
local wr_pidfile="$DATADIR/"`hostname`"-recover.pid" |
|
|
- local wr_options="--log_error='$wr_logfile' --pid-file='$wr_pidfile'" |
+ local wr_options="--disable-log-error --pid-file='$wr_pidfile'" |
|
|
log_notice "WSREP: Running position recovery with $wr_options" |
|
|
- eval_log_error "$mysqld_cmd --wsrep_recover $wr_options" |
+ eval_log_error "$mysqld_cmd --wsrep_recover $wr_options 2> $wr_logfile" |
|
|
local rp="$(grep 'WSREP: Recovered position:' $wr_logfile)" |
if [ -z "$rp" ]; then |
So I replaced mysqld_safe with version 10.2.7_1 and now I can start it up.
I don't see mysqld_safe from 10.2.7_1 has any problems. Why change it in 10.2.9?
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- is caused by
-
-
- Closed
-