Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.1.28, 10.2.9
-
None
-
10.2.10, 10.1.30
Description
Could not open required defaults file: /home/a/mariadb-environs/m1-system2/dt/--defaults-file=/home/a/mariadb-environs/m1-system2/my.cnf
|
Fatal error in defaults handling. Program aborted
|
2017-09-30 13:54:05 140004965337856 [ERROR] WSREP: Process completed with error: wsrep_sst_mysqldump --address '192.168.1.183:3308' --port '3308' --local-port '3307' --socket '/home/a/mariadb-environs/m1-system2/dt/my.sock' --defaults-file '/home/a/mariadb-environs/m1-system2/my.cnf' --gtid '9587a0be-a5b0-11e7-ab7b-2b5aa1592648:0' --gtid-domain-id '0': 1 (Operation not permitted)
|
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
- links to
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Andrii Nikitin [ anikitin ] | Sachin Setiya [ sachin.setiya.007 ] |
| Status | Open [ 1 ] | Confirmed [ 10101 ] |
| Affects Version/s | 10.2.9 [ 22611 ] |
| Fix Version/s | 10.2 [ 14601 ] |
It looks 10.2 is affected as well, just it doesn't pass --defaults-file parameter by default, so the error is harder to trigger.
| Remote Link | This issue links to "#457 wrep_sst_common and wsrep_sst_xtrabackup-v2 bugfixes to read sst parameters from configs (Web Link)" [ 28048 ] |
| Sprint | 10.2.10 [ 183 ] |
Oh I also missed that INNOMOVE also has --defaults-file in wsrep_sst_xtrabackup-v2 , which results in error in 10.1.28:
+ eval 'innobackupex --defaults-file=--defaults-file=/home/a/env1/m2-10.1.28/my.cnf --defaults-group=mysqld --no-version-check --datadir=/home/a/env1/m2-10.1.28/dt/ --move-back --force-non-empty-directories ${DATA} &>${DATA}/innobackup.move.log' |
And then in log:
Could not open required defaults file: /home/a/env1/m2-10.1.28/dt/--defaults-file=/home/a/env1/m2-10.1.28/my.cnf
|
so it must be fixed as well (or is it wsrep_sst_common which passes that incorrectly?)
| Link |
This issue is duplicated by |
| Summary | sst_mysqldump handles WSREP_SST_OPT_CONF incorrectly | sst mysqldump and xtrabackup-v2 handle WSREP_SST_OPT_CONF incorrectly |
| Assignee | Sachin Setiya [ sachin.setiya.007 ] | Sergei Golubchik [ serg ] |
| Link |
This issue relates to |
| Status | Confirmed [ 10101 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Stalled [ 10000 ] |
| Fix Version/s | 10.2.10 [ 22615 ] | |
| Fix Version/s | 10.2 [ 14601 ] | |
| Fix Version/s | 10.1 [ 16100 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Stalled [ 10000 ] | Closed [ 6 ] |
Confirmed that current 10.1 is affected (build 17290) in this line https://github.com/MariaDB/server/blob/40756c9151a564b57f351111d7486b4d18ef5e39/scripts/wsrep_sst_xtrabackup-v2.sh#L868
E.g. test test galera_sst_xtrabackup-v2_encrypt_with_key show invalid value for the parameter:
Evaluating innobackupex --defaults-file=--defaults-file=/home/a/env3/mariadb-environs/_depot/m-tar/10.1-17290/mysql-test/var/my.cnf
|
both 5.5-galera and 10.0-galera are not affected. I am re-opening this ticket and let serg decide whether it may be re-closed and needs another ticket.
| Resolution | Fixed [ 1 ] | |
| Status | Closed [ 6 ] | Stalled [ 10000 ] |
| Fix Version/s | 10.1 [ 16100 ] |
| Assignee | Sergei Golubchik [ serg ] | Andrii Nikitin [ anikitin ] |
| Status | Stalled [ 10000 ] | In Review [ 10002 ] |
| Assignee | Andrii Nikitin [ anikitin ] | Sergei Golubchik [ serg ] |
| Status | In Review [ 10002 ] | Stalled [ 10000 ] |
| Sprint | 10.2.10 [ 183 ] | 10.2.10, 10.1.30 [ 183, 215 ] |
| Rank | Ranked higher |
| Fix Version/s | 10.1.30 [ 22637 ] | |
| Fix Version/s | 10.2.12 [ 22810 ] | |
| Fix Version/s | 10.1 [ 16100 ] | |
| Fix Version/s | 10.2.10 [ 22615 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Stalled [ 10000 ] | Closed [ 6 ] |
| Workflow | MariaDB v3 [ 82872 ] | MariaDB v4 [ 152922 ] |
Note that wsrep_sst_xtrabackup doesn't have --defaults-file keyword when using WSREP_SST_OPT_CONF (defined by wsrep_sst_common) :
While wsrep_sst_mysqldump still uses it with --defaults-file :