You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
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
The text was updated successfully, but these errors were encountered: