summaryrefslogtreecommitdiff
path: root/scripts/galera_recovery.sh
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-12301: galera_recovery use @sbindir@ macro for mysqldMichal Schorm2018-01-301-1/+1
|
* MDEV-10767 /tmp/wsrep_recovery.${RANDOM} file created in unallowed SELinux ↵sachin2017-09-211-1/+1
| | | | | | | | | | | context Problem:- To create file in /tmp dir mysqld require permission initrc_tmp_t. And mysqld does not have his permission. Solution:- Instead of giving mysqld permission of initrc_tmp_t , we redirected log to file in /tmp dir through shell. I also removed a earlier workarround in mysqld_safe.sh , which create tmp log file in datadir.
* MDEV-10396: MariaDB does not restart after upgrade on debian 8Nirbhay Choubey2016-07-271-1/+2
| | | | | | | | | | | | During wsrep position recovery, galera_recovery.sh script redirected mysqld's error log to a temporary file in order to find the start position. This, however, will not work if --log-error is configured for the server. Fixed by using --log-error in command line instead of redirection. [Patch contributed by Philippe MARASSE]
* MDEV-10004: Galera's pc.recovery process fails in 10.1 with systemdNirbhay Choubey2016-06-271-0/+118
Galera recovery process works in two phases. In the first phase, mysqld is started as non-daemon with --wsrep-recover to recover and fetch the last logged global transaction ID. This ID is then used in second phase as the start position (--wsrep-start-position=XX) to start mysqld as daemon. As this process was implemented in mysqld_safe script, the recovery did not work when server was started using systemd. Fixed by introducing a shell script (wsrep_recovery.sh) that mimics the first phase of the recovery process.