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

percona-cluster-5.7.43 crashes on 2023Q4 #381

Open
xmerlin opened this issue May 4, 2024 · 3 comments
Open

percona-cluster-5.7.43 crashes on 2023Q4 #381

xmerlin opened this issue May 4, 2024 · 3 comments
Assignees

Comments

@xmerlin
Copy link

xmerlin commented May 4, 2024

Testing percona-cluster-5.7.43 from the 2023Q4 release, I realized that the mysql client crashes due to the utf settings. The client looks for /usr/lib/locale/C.UTF8/LC_CTYPE/LCL_DATA instead of /usr/lib/locale/C.UTF-8/LC_CTYPE/LCL_DATA.

ioctl(0, TIOCGWINSZ, 0xFFFFF9FFFFDFF638) = 0 ioctl(0, TIOCSWINSZ, 0xFFFFF9FFFFDFF638) = 0 Received signal #20, SIGWINCH [default] siginfo: SIG#0 ioctl(0, TCGETS, 0xFFFFF9FFFFDFF640) = 0 open("/usr/lib/locale//C.UTF8/LC_CTYPE/LCL_DATA", O_RDONLY) Err#2 ENOENT Incurred fault #6, FLTBOUNDS %pc = 0xFFFFF9FFEEFC5D70 siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000 Received signal #11, SIGSEGV [default] siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000

@xmerlin
Copy link
Author

xmerlin commented May 4, 2024

By setting it manually, the crash disappears

export LC_ALL="en_US.UTF-8"

@jperkin
Copy link
Collaborator

jperkin commented May 8, 2024

Do you know where "C.UTF-8" is coming from? I can't see it in any of the percona-cluster source code. Is there any chance it's set in your environment?

@jperkin jperkin self-assigned this May 8, 2024
@xmerlin
Copy link
Author

xmerlin commented May 12, 2024

no it's not ...I've tested all using a clean zone

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

No branches or pull requests

2 participants