Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Segmentation fault when using defaults-file option #533

Closed
zj5220924 opened this issue Dec 29, 2021 · 5 comments · Fixed by #552
Closed

[BUG] Segmentation fault when using defaults-file option #533

zj5220924 opened this issue Dec 29, 2021 · 5 comments · Fixed by #552
Labels

Comments

@zj5220924
Copy link

zj5220924 commented Dec 29, 2021

/usr/bin/mydumper --defaults-file=/data/mysql/3306/my.cnf -u test -p test -e -c -v 3 -r 5000 -l 10 -K -G -E -R -t 5 --regex='^(?!(sys.|mysql.|test.))' -o /data/dump/2021-12-29T16:07:05 -L /data/dump/2021-12-29T16:07:05/mydumper.log

** (mydumper:29000): WARNING **: Failed to load config file: Key file contains line 'skip-name-resolve' which is not a key-value pair, group, or comment
Segmentation fault

@zj5220924
Copy link
Author

mydumper --version
mydumper 0.11.5, built against MySQL 5.7.34-37

@davidducos
Copy link
Member

davidducos commented Dec 29, 2021

Hi @zj5220924, thank you for reporting this bug! Can you share the content of the default config file?

@zj5220924
Copy link
Author

zj5220924 commented Dec 30, 2021

Hi @zj5220924, thank you for reporting this bug! Can you share the content of the default config file?

Yes, I already put the mysql defaults config file into my note:
url:http://note.youdao.com/noteshare?id=37964ac81e1e80deb29c6446fe3bd69a&sub=44DF81CEE2B5496E9098E9A23FC1796D

mysql version: 5.7.27

@fliespl
Copy link

fliespl commented Dec 30, 2021

@davidducos
I had segmentation fault when I executed like this:

mydumper -o dump -c -e -h 127.0.0.1 -u $DB_USER -p $DB_PASS $DB_NAME

instead of:

mydumper -o dump -c -e -h 127.0.0.1 -u $DB_USER -p $DB_PASS -B $DB_NAME (missing -B switch).

Probably related?

@davidducos
Copy link
Member

Oh!!! I found the problem, currently --stream which is being set by default when you use DB_NAME doesn't support compression!!
This should work:

mydumper -o dump  -e -h 127.0.0.1 -u $DB_USER -p $DB_PASS $DB_NAME

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants